Farya L. Maerten 2597eeae70 Add key to control if a container can get started by its pod ... By default today, the container is always started if its pod is also started. This prevents to create custom with systemd where containers in a pod could be started through their `[Install]` section. We add a key `StartWithPod=`, enabled by default, that enables one to disable that behavior. This prevents the pod service from changing the state of the container service. Fixes #24401 Signed-off-by: Farya L. Maerten <me@ltow.me>		2024-11-05 08:39:23 +01:00
..
podman	ps: fix display of exposed ports	2024-10-23 15:03:30 +02:00
podman-mac-helper	rewrite typo osascript	2024-09-12 14:57:55 +01:00
podman-testing	set !remote build tags where needed	2024-08-19 11:41:28 +02:00
podman-wslkerninst	Fix Lint on Windows and enable the job	2024-02-20 08:06:18 -05:00
quadlet	Add key to control if a container can get started by its pod	2024-11-05 08:39:23 +01:00
rootlessport	update github.com/rootless-containers/rootlesskit to v2	2024-04-05 12:25:02 +02:00
winpath	Fix Lint on Windows and enable the job	2024-02-20 08:06:18 -05:00