Closed eriksjolund closed 2 years ago
Observation 1:
I repeated the first test (i.e. see user test103 above) but now with --log-level=debug
.
The command systemd-cgls --no-pager -u user-$(id -u).slice
was also run.
Observation 2: When I create a new user and log in to it in a virtual console and run startx
and open gnome-terminal and run the command podman version > /tmp/version
:
$ podman version > /tmp/version
WARN[0000] Failed to add pause process to systemd sandbox cgroup: Process org.freedesktop.systemd1 exited with status 1
the command prints a warning.
Observation 3:
It's probably not related to crun
because adding --runtime=/usr/bin/runc
also fails.
(i.e. podman --runtime=/usr/bin/runc build -t test /tmp/e
)
Can you check the DBUS_SESSION_BUS_ADDRESS
env var before and after startx?
I created a new user test116.
Before running startx
:
[test116@laptop ~]$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1076/bus
[test116@laptop ~]$
After running startx
:
[test116@laptop ~]$ env | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-DsJFFOMkeM,guid=0e60e9cba232e976ea3e5c326224bbc9
[test116@laptop ~]$
https://bugzilla.redhat.com/show_bug.cgi?id=1622259 This is not a podman bug.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman build
fails after opening a virtual console and runningstartx
. The error message is:The same Dockerfile builds successfully if
startx
is not run before.Steps to reproduce the issue:
As root run
Switch to a virtual console by pressing Ctrl-Alt-F3
Log in with the user test103
Run
startx
Open gnome-terminal
Create the file /tmp/e/Dockerfile with the content
by running these commands
Build the container image
Describe the results you received:
The error message
Describe the results you expected:
No error message
Additional information you deem important (e.g. issue happens only occasionally):
I also tried creating the new user test104 and logged in to another virtual console. I skipped running
startx
and instead ranpodman build -t test /tmp/e
directly. It worked.As root run
Switch to a virtual console by pressing Ctrl-Alt-F4
Log in with the user test104
Build the container image
The command succeeded.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes