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
For unit files placed in subdirectories within /etc/containers/systemd/users/${UID}/ and the other user unit search paths, Quadlet will recursively search and run the unit files present in these subdirectories.
This suggests to me that quadlets stored in /etc/containers/systemd/users/postgres/postgres.container should be generated into a systemd unit. Currently, this is not happening.
Only quadlets directly in /etc/containers/systemd/users are generated, and subdirectories are skipped over.
This did used to work, and I'm not quite sure when this behaviour changed.
Steps to reproduce the issue
Steps to reproduce the issue
Copy the contents of this directory into /etc/containers/systemd/users/postgres
Run /usr/lib/systemd/system-generators/podman-system-generator --user --dryrun
Notice how the Postgres quadlet was not found
Describe the results you received
Subdirectories of the user unit search paths are ignored.
Describe the results you expected
I would have expected subdirectories of the user unit search paths to have been detected (as declared in the docs), and for a systemd unit to have been generated.
podman info output
host:
arch: amd64buildahVersion: 1.38.0cgroupControllers:
- cpu
- io
- memory
- pidscgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.12-3.fc41.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 98.97systemPercent: 0.48userPercent: 0.56cpus: 24databaseBackend: sqlitedistribution:
distribution: fedoravariant: silverblueversion: "41"eventLogger: journaldfreeLocks: 2047hostname: fedoraidMappings:
gidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536uidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536kernel: 6.11.6-300.fc41.x86_64linkmode: dynamiclogDriver: journaldmemFree: 1136812032memTotal: 33362931712networkBackend: 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.0-1.fc41.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.13.0ociRuntime:
name: crunpackage: crun-1.18.1-1.fc41.x86_64path: /usr/bin/crunversion: |- crun version 1.18.1 commit: c41f034fdbb9742c395085fc98459c94ad1f9aae rundir: /run/user/1000/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241121.g238c69f-1.fc41.x86_64version: | pasta 0^20241121.g238c69f-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/user/1000/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: trueseccompEnabled: 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: 8589668352swapTotal: 8589930496uptime: 92h 28m 16.00s (Approximately 3.83 days)variant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
ghcr.io/rsturla:
Blocked: falseInsecure: falseLocation: ghcr.io/rsturlaMirrorByDigestOnly: falseMirrors:
- Insecure: trueLocation: localhost:5000/rsturlaPullFromMirror: ""Prefix: ghcr.io/rsturlaPullFromMirror: ""localhost:5000:
Blocked: falseInsecure: trueLocation: localhost:5000MirrorByDigestOnly: falseMirrors: nullPrefix: localhost:5000PullFromMirror: ""search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.iostore:
configFile: /var/home/admin/.config/containers/storage.confcontainerStore:
number: 1paused: 0running: 1stopped: 0graphDriverName: overlaygraphOptions: {}graphRoot: /var/home/admin/.local/share/containers/storagegraphRootAllocated: 1998678130688graphRootUsed: 823130402816graphStatus:
Backing Filesystem: btrfsNative Overlay Diff: "true"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "false"imageCopyTmpDir: /var/tmpimageStore:
number: 61runRoot: /run/user/1000/containerstransientStore: falsevolumePath: /var/home/admin/.local/share/containers/storage/volumesversion:
APIVersion: 5.3.1Built: 1732147200BuiltTime: Thu Nov 21 00: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
Podman running on Fedora Silverblue
Additional information
No response
The text was updated successfully, but these errors were encountered:
Issue Description
From the quadlet documentation:
This suggests to me that quadlets stored in
/etc/containers/systemd/users/postgres/postgres.container
should be generated into a systemd unit. Currently, this is not happening.Only quadlets directly in
/etc/containers/systemd/users
are generated, and subdirectories are skipped over.This did used to work, and I'm not quite sure when this behaviour changed.
Steps to reproduce the issue
Steps to reproduce the issue
/etc/containers/systemd/users/postgres
/usr/lib/systemd/system-generators/podman-system-generator --user --dryrun
Describe the results you received
Subdirectories of the user unit search paths are ignored.
Describe the results you expected
I would have expected subdirectories of the user unit search paths to have been detected (as declared in the docs), and for a systemd unit to have been generated.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Podman running on Fedora Silverblue
Additional information
No response
The text was updated successfully, but these errors were encountered: