-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd crashes while attempting to start under container_user_r role #282
Comments
UpdateRootless Podman also won't work under
Then the
I have no idea what's happening with SELinux. I literally stuck now |
Update 2Running under |
What version of podman are you attempting this with? |
At that time, Podman is up-to-date. I believe v4.7.2. |
Could you try again to make sure it is 4.7.2 or better yet 4.8.* |
I'm going to re-install Fedora Server again after finished my work today and I'll tell you the result. Thank you for your attention |
I re-installed the latest stable Fedora Server 39 and
Then login as container and I ran this command $ systemctl --user status
-bash: systemctl: command not found
$ ls $(which systemctl)
/usr/bin/which: no systemctl in (/home/container/.local/bin:/home/container/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin) Well... that's weird, then I went back to admin user (which is staff_u) and run this command:
Where
EditI realized that the latest package isn't actually latest
Is it still on rawhide? |
What are the latest AVC messages you are seeing? |
That's odd... perhaps this is entirely systemd bug? I also tried to logged in
And then go back to admin user to ran this
I have no idea why previous AVC messages suddenly gone after I re-installed the fedora and upgrade to latest stable. Despite of that, the
|
Dontaudit rules are hiding the denial. sudo semodule -DB Now you should see the AVCs sudo semodule -B To run the dontaudit rules back on. |
Great! It's starting to show something. For curiosity reason, I tried same command in permissive mode to get more denial information.
EDITI just figured out what happened after stored the last logs above as
Running |
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
The pull request fixes issue containers#282 Signed-off-by: Athaariq Ardhiansyah <[email protected]>
Hello Mr. Dan and Colleagues,
Currently, I'm trying to run podman containers on multiple users with
container_u:container_user_r:container_user_t:s0:c512.c1023
context. For now, I'm running on fresh Fedora 39 Server Edition installation with container support option enabled. The problem is whenever I start the systemd for one of that user, the systemd crashes withSEGV
or segmentation fault error.Then I tried to troubleshoot it with
ausearch
as belowI have no idea why sudoers are not allowed to search for
/proc
directory and causes segfault on systemd. Did I do something wrong on configuration or AVC report says nothing about the crash? By the way, I noticed something funny...Is systemd intentionally disabled in
container_user_r
role? If yes, how do I auto-start each podman container on multiple users? Thank you!The text was updated successfully, but these errors were encountered: