Using Podman Desktop to start a container, makes the Quadlet Extension break on Quadlet creation

[deversmann]

I have tested this with Podman 5.3.2 and Podman 5.4.0-rc2. I am using Podman Desktop on an M1 MacBook Pro. When you start a container using podman run, the quadlet extension functions as expected and creates a well formed quadlet file. However, if you use Podman Desktop to start the container, the quadlet creation errors out because Podman Desktop uses APIs to start the container and the CreateCommand field is not set in the podman inspect output. With 5.4.0-rc2 it is an actual error. In 5.3.2, it is just an incorrect quadlet as the CreateCommand field is incorrectly populated.

see containers/podlet#134

[axel7083]

Thanks for reporting, this is a known limitation of Podlet, not sure what we could do.

Maybe the Podlet logic could be changed to use the ContainerInspect content to generate the Quadlet instead of the CreateCommand, in theory we should have all the needed information.

[deversmann]

That makes sense. The CreateCommand was likely the easiest path since it has everything in one place.