when running centos7 image in docker, error
[root@2181bc14e47f /]# systemctl list-units
Failed to get d-bus connection: No such file or directory
d-bus allows the program to register on it to provide services to other programs. It also provides the possibility for the client program to query what services are available. Applications can also be registered to wait for kernel events, such as hardware hotplug. It is a three-tier inter-process communication (IPC) system, including:
function library libdbus, used for calling contacts and interacting messages between two applications. A message constructed based on libdbus, the bus daemon can connect to multiple applications simultaneously and can route messages from one application to 0 or more other programs. A series of Wrapper libraries based on specific application frameworks. D-bus is designed for two specific situations:
communication between two desktop applications within the same desktop session, allowing the desktop session to be integrated as a whole to solve problems related to the process lifecycle. Communication between a desktop session and an operating system, where the operating system generally includes the kernel and system daemons.
after the docker exit
$docker run — br> $docker run –privileged/ti-e “container=docker” centos7-base /usr/sbin/init
-privileged docker introduction, using this parameter, the root in the container has the real root privilege, otherwise, the root in the container is just an external ordinary user privilege. The container that the Privileged starts can see a lot of equipment on host and mount can be performed.
even allows you to start a docker container in a docker container. -e “container=docker” sets the environment variable that processes inside the container can get directly.
can now execute the systemctl command
/root @ bd5aa199dbc9 ~ # systemctl status SSHD
low SSHD. Service – the OpenSSH server daemon
the Loaded: the Loaded (/ usr/lib/systemd/system/SSHD. Service; enabled; Vendor pre: enabled)
Active: inactive (dead)
Docs: man: SSHD (8)
man:sshd_config(5)
Read More:
- linux docker Error Failed to get D-Bus connection: Operation not permitted
- sh: 0: getcwd() failed: No such file or directory
- Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory (How to Fix)
- How to Fix Module build failed: Error: ENOENT: no such file or directory, scandir xxxxxx\node_…
- No code, a solution to the error in the path of reading CSV file by Python: filenotfounderror: [errno 2] no such file or directory: ‘XX. CSV‘
- Error “/run/lvm/lvmetad.socket: connect failed: No such file or directory” – but not Grub related
- Solve syntax error: unexpected end of file or /bin/bash^m: bad interpeneter: no match file or directory
- Solution to error opening trace file: no such file or directory (2) in Android
- Ubuntu error: flAbsPath on /var/lib/dpkg/status failed – realpath (2: No such file or directory)
- How to solve the problem of “unable to open include file:” graphics. H “: no such file or directory”
- Docker CentOS Failed to get D-Bus connection: Operation not permitted
- Importerror of [docker] error: libGL.so .1: cannot open shared object file: No such file or directory
- Docker load loading mirror message JSON no such file or directory error
- Cannot open include file: ‘io.h‘: No such file or directory
- Error occurred when Python installed the pocketsphinx module (package): Command‘ swig.exe “Failed: no such file or directory
- VS2010 compiler can’t open include file: “GL / glaux. H”: no such file or directory
- Ubuntu 64 prompts bash: no such file or directory file exists
- Failed to connect to Mir:Failed to connect to server socket:No such file or directory
- In VS2010, the compiler cannot open the file “GL / glaux. H”: no such file or directory
- docker service Failed to get D-Bus connection: Operation not permitted