Podlet should use the Pod option for Container Quadlets

[paulcalabro]

https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html#container-units-container

e.g., Pod=pod-name

Instead, it's using PodmanArgs.

e.g.,

podlet podman run --pod test-deployment alpine:latest

or

podlet podman run --pod test-deployment.pod alpine:latest

# alpine.container
[Container]
Image=alpine:latest
PodmanArgs=--pod test-deployment

# alpine.container
[Container]
Image=alpine:latest
PodmanArgs=--pod test-deployment.pod

[TheRealBecks]

This feature has been introduced in #68

@k9withabone Looks like the Pod feature needs to be parsed differently when using podlet podman run --pod <name>? Bug or feature?

[k9withabone]

This is done on purpose as the Pod= Quadlet container option requires specifying a .pod Quadlet file. Podlet could allow the second example, podlet podman run --pod test-deployment.pod alpine:latest, to set Pod=, but I'm not sure if that's a good idea as someone could have a pod with a name ending in .pod.

[paulcalabro]

Thanks for taking a look.
Regarding the latter point, is that any different than a user currently being able to do the same for network like this:

podman network create bar.network --internal

podlet podman run -it --network=bar.network alpine:latest 

# alpine.container
[Container]
Image=alpine:latest
Network=bar.network
PodmanArgs=--interactive --tty

[k9withabone]

That's a fair point.

Another consideration is that the value for --pod can be prefixed with new: to instruct Podman to create the pod. I'm not sure what Podlet should do in the case where both new: and .pod are used.