Podman v5.3

[k9withabone]

Add support for features introduced in Podman v5.3.0:

• ServiceName=
  • Add podlet --service-name option when outputting a single Quadlet file?
• [Quadlet]
  • DefaultDependencies=
    • Different from DefaultDependencies= in the [Unit] section.
    • Default is true.
    • Add podlet --disable-default-quadlet-dependencies flag.
• [Container]
  • AddHost=
  • CgroupsMode=
  • HealthLogDestination=
  • HealthMaxLogCount=
  • HealthMaxLogSize=
  • StartWithPod=
    • Default is true.
    • Add podlet --no-start-with-pod flag.
  • Network=
    • Supports .container for using the network of another container.
    • Compose network_mode: "service:service_name" can now be converted.
• [Pod]
  • AddHost=
  • DNS=
  • DNSOption=
  • DNSSearch=
  • GIDMap=
  • IP=
  • IP6=
  • SubGIDMap=
  • SubUIDMap=
  • UIDMap=
  • UserNS=
• [Build]
  • ImageTag=
    • Can now be set multiple times.

[k9withabone]

@TheRealBecks do you agree with adding the Podlet options I listed? I'm unsure about podlet --service-name.

[TheRealBecks]

@TheRealBecks do you agree with adding the Podlet options I listed? I'm unsure about podlet --service-name.

After checking containers/podman#23414 and containers/podman#23427 I understood that the ServiceName is meant to be used with .pod unit files only. Do you agree?

If so I would suggest to also introduce this command to Podlet for .pod files.

[k9withabone]

After checking containers/podman#23414 and containers/podman#23427 I understood that the ServiceName is meant to be used with .pod unit files only. Do you agree?

It seems to me that was how it was originally designed (because it was easier) but was later expanded to all Quadlet files. In the release notes it says ServiceName was added to all, and it is documented for all Quadlet file types in their respective sections. Also, I just tested it locally and it seems to work for all types.

[k9withabone]

What about podlet --no-default-quadlet-dependencies and podlet --no-start-with-pod? Should I add them? Is the wording of the flags good?

[TheRealBecks]

It seems to me that was how it was originally designed (because it was easier) but was later expanded to all Quadlet files. In the release notes it says ServiceName was added to all, and it is documented for all Quadlet file types in their respective sections. Also, I just tested it locally and it seems to work for all types.

I checked again in the latest documentation and it can be used within [Pod] and [Artifact], but nothing else? So I think in the release notes they meant that the value of ServiceName will be used in all to be generated Quadlet files where possible? Keep in mind that they had a podman generate systemd command in version 5.3.

What about podlet --no-default-quadlet-dependencies and podlet --no-start-with-pod? Should I add them? Is the wording of the flags good?

The question here is: Do you want to introduce arguments starting with no or do you want to use --default-quadlet-dependencies=False? I checked the Podlet help and I can't see the no arguments. But I also can't see arguments that require boolean values, but arguments like --overwrite that will be True by default. Soo.... maybe it's good to introduce --no? But the wording of the flags is good 👍

[k9withabone]

I checked again in the latest documentation and it can be used within [Pod] and [Artifact], but nothing else? So I think in the release notes they meant that the value of ServiceName will be used in all to be generated Quadlet files where possible?

Huh, I think the documentation is incorrect because I just tested it with all the Quadlet file types, and it works for all of them.

[k9withabone]

Found containers/podman#27015, so this is a known issue. Looks like work on the fix was started while they were trying to separate the Quadlet docs into separate parts which was later reverted and work on the fix stalled.