socat[646] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused

[veggiemonk]

Hi,

Can anyone help me? I have a problem with socat apprently.

$> sudo docker run --privileged -v /var/lib/docker -t -i ewindisch/dockenstack

 * Starting message broker rabbitmq-server                                               140609 19:28:05 mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.
140609 19:28:05 mysqld_safe Logging to '/var/log/mysql/error.log'.
140609 19:28:05 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
                                                                                  [ OK ]
2014/06/09 19:28:09 socat[646] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/06/09 19:28:09 docker daemon: 0.12.0 14680bf; execdriver: native; graphdriver:
[95da4ad2] +job serveapi(unix:///var/run/docker.sock)
[95da4ad2] +job initserver()
[95da4ad2.initserver()] Creating server
2014/06/09 19:28:09 Listening for HTTP on unix (/var/run/docker.sock)
[95da4ad2] +job init_networkdriver()
[95da4ad2.init_networkdriver()] creating new bridge for docker0
[95da4ad2.init_networkdriver()] getting iface addr
[95da4ad2] -job init_networkdriver() = OK (0)
Error loading docker apparmor profile: exec: "/sbin/apparmor_parser": stat /sbin/apparmor_parser: no such file or directory ()
[95da4ad2] -job initserver() = ERR (1)
2014/06/09 19:28:10 Error loading docker apparmor profile: exec: "/sbin/apparmor_parser": stat /sbin/apparmor_parser: no such file or directory ()
2014/06/09 19:28:10 socat[677] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/06/09 19:28:11 socat[681] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/06/09 19:28:12 socat[685] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/06/09 19:28:13 socat[689] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
^C%

Any help would be appreciated.

[Phi-Ho]

+1

[msabramo]

I just got this too.

❯ docker run --privileged -t -i ewindisch/dockenstack
 * Starting message broker rabbitmq-server                                                                                                                                      140707 16:39:57 mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.
140707 16:39:57 mysqld_safe Logging to '/var/log/mysql/error.log'.
140707 16:39:57 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
                                                                                                                                                                         [ OK ]
2014/07/07 16:39:59 socat[602] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/07/07 16:39:59 docker daemon: 0.12.0 14680bf; execdriver: native; graphdriver:
[6537de13] +job initserver()
[6537de13.initserver()] Creating server
[6537de13] +job serveapi(unix:///var/run/docker.sock)
2014/07/07 16:39:59 Listening for HTTP on unix (/var/run/docker.sock)
[6537de13] +job init_networkdriver()
[6537de13.init_networkdriver()] creating new bridge for docker0
[6537de13.init_networkdriver()] getting iface addr
[6537de13] -job init_networkdriver() = OK (0)
Error loading docker apparmor profile: exec: "/sbin/apparmor_parser": stat /sbin/apparmor_parser: no such file or directory ()
[6537de13] -job initserver() = ERR (1)
2014/07/07 16:40:02 Error loading docker apparmor profile: exec: "/sbin/apparmor_parser": stat /sbin/apparmor_parser: no such file or directory ()
2014/07/07 16:40:02 socat[638] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/07/07 16:40:03 socat[642] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/07/07 16:40:04 socat[646] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/07/07 16:40:05 socat[650] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused

[jpeeler]

Update: actually, I'm pretty sure this is related to SELinux errors that I missed earlier.

$ docker run -privileged -t -i ewindisch/dockenstack
<downloading snipped>
 * Starting message broker rabbitmq-server                                      140711 18:06:24 mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.
140711 18:06:24 mysqld_safe Logging to '/var/log/mysql/error.log'.
140711 18:06:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
                                                                         [ OK ]
2014/07/11 18:06:27 socat[645] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused
2014/07/11 18:06:27 docker daemon: 0.12.0 14680bf; execdriver: native; graphdriver: 
[84794aec] +job serveapi(unix:///var/run/docker.sock)
[84794aec] +job initserver()
[84794aec.initserver()] Creating server
2014/07/11 18:06:27 Listening for HTTP on unix (/var/run/docker.sock)
[error] attach_loopback.go:42 There are no more loopback device available.
loopback mounting failed
[84794aec] -job initserver() = ERR (1)
2014/07/11 18:06:27 loopback mounting failed
2014/07/11 18:06:28 socat[655] E connect(3, AF=1 "/var/run/docker.sock", 22): Connection refused

[asajeffrey]

The problem is:

/sbin/apparmor_parser: no such file or directory ()

caused by the container not loading the apparmor package. The Dockerfile contains:

RUN apt-get -qqy install apparmor

but the image on the docker repository doesn't include apparmor:

$ docker run --privileged -t -i ewindisch/dockenstack /bin/bash root@4d18129eb3ac:/# dpkg -l apparmor un apparmor (no description available)

The reason for the discrepancy is in the build history (https://registry.hub.docker.com/u/ewindisch/dockenstack/builds_history/7634/). The public dockenstack image hasn't succesfully built since 8 June 2014, it has reported an Error status since then:

build Id Status Created Date Last Updated buptro3ucupteenq44vfkwm Error 2014-08-05 19:57:35 2014-08-05 20:02:02

I'm going to try to build dockenstack locally to see if this fixes the problem.

[jpeeler]

@asajeffrey - what was the result of your rebuild?

[arnaudmorinol]

apparently, you just need to launch docker with --privileged instead of -privileged to get rid of this error

[r1chardj0n3s]

Just a note: this is not related to the --privileged flag; using it does not resolve this error.

[GastonMazzei]

If someone could tell what was the result of the rebuild I would be much grateful