check access rights for systemd-related config options #580
Comments
|
@giuseppe @vrothberg is there an easy way for us to check so that containers-common/pkg/config can set the defaults. Perhaps check if /proc/1 == /proc/self? Then we know we are in a container without systemd, so set the defaults to non systemd defaults? |
rhatdan
added a commit
to rhatdan/common
that referenced
this issue
May 26, 2021
Currently we have users failing to run containers within containers or on systems without systemd support. This change will give us better defaults on these systems. Fixes: containers#580 Signed-off-by: Daniel J Walsh <[email protected]>
|
#585 did not fix that, see #585 (review). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some config knobs require access to systemd/DBUS etc. (e.g., cgroups-manager, logger, eventer). In those cases, we should check early on if we have access rights to systemd/DBUS.
In the past week we hit two Podman issues (customer portal and upstream), where the rootless users did not have access rights. One could be solved with
su --loginbut the other could not.Checking early will protect users from facing all kinds of errors from all kinds of execution paths and allows us to give some meaningful error message and help them resolve the isssue (e.g., using --login with su, or pointing out that user is missing group access).
From the debugging session in containers/podman#10308
@rhatdan PTAL
The text was updated successfully, but these errors were encountered: