-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.4
-
None
-
None
-
None
-
rhel-sst-container-tools
-
3
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
Before updating to RHEL9.4 I had no problems running buildah with an dedicated user account with "linger" enabled.
$ buildah images
REPOSITORY TAG IMAGE ID CREATED SIZE
after updating to RHEL9.4 I get following warning (as I wrote, the user has a running dbus session ( enabled linger ).
$ buildah images
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to log in using a user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1201` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available
WARN[0000] For using systemd, you may need to log in using a user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl enable-linger 1201` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
REPOSITORY TAG IMAGE ID CREATED SIZE
{{when doing }}
$ export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus
The warning message is gone.
This was not necessary in RHEL9.3.
"podman images" does not show such warning message.
Please provide the package NVR for which bug is seen:
podman-4.9.4-3.el9_4.x86_64
buildah-1.33.7-1.el9_4.x86_64
container-tools-1-14.el9.noarch
How reproducible:
everytime
Steps to reproduce
- # useradd test
- # loginctl enable-linger test
- $ buildah images
Expected results
No warning messages
Actual results
warning messages like above