Bug ID | 1208510 |
---|---|
Summary | podman/quadlet generating services with wrong podman binary path |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | x86-64 |
OS | openSUSE Tumbleweed |
Status | NEW |
Severity | Minor |
Priority | P5 - None |
Component | Containers |
Assignee | containers-bugowner@suse.de |
Reporter | danish.prakash@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Reported by bburky: I wanted to test out the new quadlet features so I installed podman-4.4.1-2.1.aarch64 from devel:microos openSUSE_Factory_ARM. I'm seeing the same symptoms as this bug report: Quadlet generating services with wrong podman path https://github.com/containers/podman/issues/17359 When using a *.container file, the quadlet/podman-system-generator generated systemd unit uses /usr/local/bin/podman instead of /usr/bin/podman. The suggested fix (as was applied to Archlinux) seems to be setting PREFIX when calling make. Also, the quadlet feature appears to unconditionally use the crun runtime instead of the default runtime (currently runc), so it may need to be installed too if this feature is used. (Not sure if this is an upstream bug or intentional.) https://github.com/containers/podman/blob/bac20d1917622fa45130427c78231e2529ba328e/pkg/systemd/quadlet/quadlet.go#L317-L321