You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to reopen bug #23381: setting PodName doesn't help.
When trying to create a Container with the Pod field set to PodName, where PodName is the name of a pod defined by a podname.pod file and containing PodName=podname, podman-system-generator throws the following error:
converting "mycontainer.container": pod podname is not Quadlet based
$/usr/lib/systemd/system-generators/podman-system-generator --user --dryrun
> quadlet-generator[5849]: Loading source unit file /etc/containers/systemd/user/1012/auto-dev.pod
> quadlet-generator[5849]: Loading source unit file /etc/containers/systemd/user/1012/db-dev.container
> quadlet-generator[5849]: Loading source unit file /etc/containers/systemd/user/1012/n8n-dev.container
> ---auto-dev.service---
> [Unit]
> Wants=podman-user-wait-network-online.service
> After=podman-user-wait-network-online.service
> Requires=podman.socket
> After=podman.socket
> Description=n8n automation pod
> SourcePath=/etc/containers/systemd/user/1012/auto-dev.pod
> RequiresMountsFor=%t/containers
>
> [Install]
> WantedBy=default.target
>
> [X-Pod]
> PublishPort=5432:5432
> PublishPort=2443:1443
> PodName=auto-dev
> ServiceName=auto-dev
>
> [Service]
> SyslogIdentifier=%N
> ExecStart=/usr/bin/podman pod start --pod-id-file=%t/%N.pod-id
> ExecStop=/usr/bin/podman pod stop --pod-id-file=%t/%N.pod-id --ignore --time=10
> ExecStopPost=/usr/bin/podman pod rm --pod-id-file=%t/%N.pod-id --ignore --force
> ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile=%t/%N.pid --pod-id-file=%t/%N.pod-id --exit-policy=stop --replace --publish 5432:5432 --publish 2443:1443 --infra-name auto-dev-infra --name auto-dev
> Environment=PODMAN_SYSTEMD_UNIT=%n
> Type=forking
> Restart=on-failure
> PIDFile=%t/%N.pid
>
> quadlet-generator[5849]: converting "db-dev.container": pod auto-dev is not Quadlet based
> converting "n8n-dev.container": pod auto-dev is not Quadlet based
Alternately, if I find/replace all instances of "auto-dev" with "auto-dev.pod" in these three files as suggested by the workaround in #23381, dry-run throws no errors. However, it's a false positive: when systemctl daemon-reload, the service auto-dev-pod is created, but not services for the containers.
Describe the results you expected
Services for each defined container running in the defined pod.
podman info output
host:
arch: amd64buildahVersion: 1.38.0cgroupControllers:
- cpuset
- cpu
- io
- memory
- hugetlb
- pids
- rdma
- misccgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.12-3.fc41.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 99.34systemPercent: 0.18userPercent: 0.48cpus: 6databaseBackend: sqlitedistribution:
distribution: fedoravariant: silverblueversion: "41"eventLogger: journaldfreeLocks: 2044hostname: consoleidMappings:
gidmap: nulluidmap: nullkernel: 6.12.5-200.fc41.x86_64linkmode: dynamiclogDriver: journaldmemFree: 28942364672memTotal: 33444179968networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.13.1-1.fc41.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.13.1package: netavark-1.13.1-1.fc41.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.13.1ociRuntime:
name: crunpackage: crun-1.19.1-1.fc41.x86_64path: /usr/bin/crunversion: |- crun version 1.19.1 commit: 3e32a70c93f5aa5fea69b50256cca7fd4aa23c80 rundir: /run/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241211.g09478d5-1.fc41.x86_64version: | pasta 0^20241211.g09478d5-1.fc41.x86_64 Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: truepath: /run/podman/podman.sockrootlessNetworkCmd: pastasecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: falseseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: trueserviceIsRemote: falseslirp4netns:
executable: /usr/bin/slirp4netnspackage: slirp4netns-1.3.1-1.fc41.x86_64version: |- slirp4netns version 1.3.1 commit: e5e368c4f5db6ae75c2fce786e31eef9da6bf236 libslirp: 4.8.0 SLIRP_CONFIG_VERSION_MAX: 5 libseccomp: 2.5.5swapFree: 8589930496swapTotal: 8589930496uptime: 1h 9m 47.00s (Approximately 0.04 days)variant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.iostore:
configFile: /usr/share/containers/storage.confcontainerStore:
number: 3paused: 0running: 2stopped: 1graphDriverName: overlaygraphOptions:
overlay.imagestore: /usr/lib/containers/storageoverlay.mountopt: nodev,metacopy=ongraphRoot: /var/lib/containers/storagegraphRootAllocated: 1022505254912graphRootUsed: 16356438016graphStatus:
Backing Filesystem: btrfsNative Overlay Diff: "false"Supports d_type: "true"Supports shifting: "true"Supports volatile: "true"Using metacopy: "true"imageCopyTmpDir: /var/tmpimageStore:
number: 5runRoot: /run/containers/storagetransientStore: falsevolumePath: /var/lib/containers/storage/volumesversion:
APIVersion: 5.3.1Built: 1732147200BuiltTime: Wed Nov 20 19:00:00 2024GitCommit: ""GoVersion: go1.23.3Os: linuxOsArch: linux/amd64Version: 5.3.1
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Fedora 41 atomic
Additional information
No response
The text was updated successfully, but these errors were encountered:
First as stated in the comment #23381 (comment) it is not a workaround. It is the required configuration (as also stated in the man page)
As for your issue, I created the files you pasted here on my machine (running the same podman version) and the service files were generated:
$ systemctl --user daemon-reload
$ systemctl --user status auto-dev
○ auto-dev.service - auto pod
Loaded: loaded (/home/yblum.linux/.config/containers/systemd/auto-dev.pod; generated)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
$ systemctl --user status db-dev
○ db-dev.service - automation db - dev
Loaded: loaded (/home/yblum.linux/.config/containers/systemd/db-dev.container; generated)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
$ systemctl --user status app-dev
○ app-dev.service - app dev server
Loaded: loaded (/home/yblum.linux/.config/containers/systemd/app-dev.container; generated)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
You pasted only part of the Quadlet files and didn't add the results of the dryrun after you've corrected the reference to the pod. Are you sure it returned successfully?
You wrote that the service auto-dev-pod was created, while the name of the service of the pod is actually auto-dev. Are you sure you are looking for the correct service names for the containers?
Issue Description
to reopen bug #23381: setting PodName doesn't help.
When trying to create a Container with the Pod field set to PodName, where PodName is the name of a pod defined by a podname.pod file and containing PodName=podname, podman-system-generator throws the following error:
converting "mycontainer.container": pod podname is not Quadlet based
Steps to reproduce the issue
Describe the results you received
Alternately, if I find/replace all instances of "auto-dev" with "auto-dev.pod" in these three files as suggested by the workaround in #23381, dry-run throws no errors. However, it's a false positive: when
systemctl daemon-reload
, the serviceauto-dev-pod
is created, but not services for the containers.Describe the results you expected
Services for each defined container running in the defined pod.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Fedora 41 atomic
Additional information
No response
The text was updated successfully, but these errors were encountered: