{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/2296","repository_url":"https://api.github.com/repos/docker/docker","labels_url":"https://api.github.com/repos/docker/docker/issues/2296/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/2296/comments","events_url":"https://api.github.com/repos/docker/docker/issues/2296/events","html_url":"https://github.com/docker/docker/issues/2296","id":21247099,"number":2296,"title":"Running systemctl in container fails with \"Failed to get D-Bus connection\"","user":{"login":"daviddavis","id":86290,"avatar_url":"https://avatars.githubusercontent.com/u/86290?v=3","gravatar_id":"","url":"https://api.github.com/users/daviddavis","html_url":"https://github.com/daviddavis","followers_url":"https://api.github.com/users/daviddavis/followers","following_url":"https://api.github.com/users/daviddavis/following{/other_user}","gists_url":"https://api.github.com/users/daviddavis/gists{/gist_id}","starred_url":"https://api.github.com/users/daviddavis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daviddavis/subscriptions","organizations_url":"https://api.github.com/users/daviddavis/orgs","repos_url":"https://api.github.com/users/daviddavis/repos","events_url":"https://api.github.com/users/daviddavis/events{/privacy}","received_events_url":"https://api.github.com/users/daviddavis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":34,"created_at":"2013-10-18T21:46:30Z","updated_at":"2016-11-17T09:43:35Z","closed_at":"2013-12-06T20:10:57Z","body":"I searched Issues and while I found other bugs that seemed similar, I couldn't tell if they were exactly the same as this so I apologize if this is a repeat.\n\nAfter following the steps on [this blog to setup docker on Fedora](http://goldmann.pl/blog/2013/09/25/docker-and-fedora/), when you run systemctl you get an error about failing to connect to dbus.\n\n```\nbash-4.2# systemctl list-units\nFailed to get D-Bus connection: No connection to service manager.\n```\n\nDocker version: docker-io-0.6.3-3.devicemapper.fc19.x86_64\nOS: Fedora 19 (Schrödinger’s Cat)\n"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/261200612","html_url":"https://github.com/docker/docker/issues/2296#issuecomment-261200612","issue_url":"https://api.github.com/repos/docker/docker/issues/2296","id":261200612,"user":{"login":"thaJeztah","id":1804568,"avatar_url":"https://avatars.githubusercontent.com/u/1804568?v=3","gravatar_id":"","url":"https://api.github.com/users/thaJeztah","html_url":"https://github.com/thaJeztah","followers_url":"https://api.github.com/users/thaJeztah/followers","following_url":"https://api.github.com/users/thaJeztah/following{/other_user}","gists_url":"https://api.github.com/users/thaJeztah/gists{/gist_id}","starred_url":"https://api.github.com/users/thaJeztah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thaJeztah/subscriptions","organizations_url":"https://api.github.com/users/thaJeztah/orgs","repos_url":"https://api.github.com/users/thaJeztah/repos","events_url":"https://api.github.com/users/thaJeztah/events{/privacy}","received_events_url":"https://api.github.com/users/thaJeztah/received_events","type":"User","site_admin":false},"created_at":"2016-11-17T09:43:35Z","updated_at":"2016-11-17T09:43:35Z","body":"@trinitronx I'd be very careful running with those options;\r\n\r\n- `privileged:true` is equivalent to `--cap-add ALL`, disabling selinux, and (iirc) disabling seccomp profiles. Effectively, the container does not provide any protection, and `root` inside the container can take over the host\r\n- `--cap-add ALL` also allows `root` inside the container to take control of the host\r\n- Because you already added `--cap-add ALL`, adding `SYS_ADMIN`, `NET_ADMIN`, `NET_BIND_SERVICE`, and `NET_BROADCAST` does nothing (these are already part of `ALL`)\r\n\r\n"}}
{"actor":{"display_login":"thaJeztah"}}