Skip to content
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

systemctl status: Failed to get D-Bus connection: Operation not permitted #7

Open
cetu86 opened this issue Oct 7, 2016 · 2 comments

Comments

@cetu86
Copy link

cetu86 commented Oct 7, 2016

I executed the docker exec command that was printed by run.sh:

docker exec -t -i 5fcd37cf1ae5652ff7f1738e0b8b7579558d4471483aad7ba6d839824e05a039 /bin/bash

Now I'm inside the container. ps shows systemd is running as PID 1:

[root@5fcd37cf1ae5 /]# ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 40408 2604 ? Ss 13:52 0:00 /usr/lib/systemd/systemd
root 7 0.0 0.0 11780 3056 ? Ss 13:52 0:00 /bin/bash
root 30 0.0 0.0 47432 3428 ? R+ 13:55 0:00 ps aux

But I can't query systemd's status:

[root@5fcd37cf1ae5 /]# systemctl status
Failed to get D-Bus connection: Operation not permitted

@stefanandres
Copy link

I have the same issue when running Docker for Mac (https://docs.docker.com/docker-for-mac/).
On Mac I still need to add --privileged to get dbus running.

I can confirm, that it is working in a "real" (even a qemu) VM running Linux does not need --privileged though.

What could be the reason? Docker for Mac is also running a Linux with the HyperKit (macOS's native virtualization) though

@djmaze
Copy link

djmaze commented Dec 2, 2016

I think this has to to with newer Docker versions which use seccomp. Adding --security-opt seccomp=unconfined makes it work again for me.

This doesn't strike me as a nice solution though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants