Comment 3 for bug 1499607

Revision history for this message
Steve Adams (sa240s) wrote :

I can make swarm master and two swarm nodes "ACTIVE", and ssh into them using ATOMIC-5. (See below).
My "container-create" fails with a docker internal error.
I'm running docker 1.8.2 on host and swarm bays running 1.7.1

Is this bug about starting containers using those swarm bays?

----------------------- example output...

stack@Steve-Magnum-AllInOne:~/devstack$ nova list
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------------------------------+
| 061562d9-ece2-470e-b121-cf5ac3b39e54 | sw-mba4vgeydz7-0-g66yrvsjskel-swarm_node-xfmgaj7epnzk | ACTIVE | - | Running | swarmbay-jf2m3wlc2jem-fixed_network-thlrqkjmi4yz=10.0.0.5, 172.24.4.6 |
| 1c1ab216-2197-47bf-b31f-9ab9e5231f93 | sw-mba4vgeydz7-1-ekfk2etlmlei-swarm_node-ojq65eq6avso | ACTIVE | - | Running | swarmbay-jf2m3wlc2jem-fixed_network-thlrqkjmi4yz=10.0.0.4, 172.24.4.5 |
| 55b3e0c0-5f62-4075-9309-0759f75e21f9 | swarmbay-jf2m3wlc2jem-swarm_master-oikqqxyccjo2 | ACTIVE | - | Running | swarmbay-jf2m3wlc2jem-fixed_network-thlrqkjmi4yz=10.0.0.3, 172.24.4.4 |
+--------------------------------------+-------------------------------------------------------+--------+------------+-------------+-----------------------------------------------------------------------+
stack@Steve-Magnum-AllInOne:~/devstack$

devstack$ magnum container-create --name test-container \
> --image cirros \
> --bay swarmbay \
> --command "ping -c 4 8.8.8.8"
ERROR: Docker internal Error: ('Connection aborted.', error(111, 'ECONNREFUSED')) (HTTP 500)
stack@Steve-Magnum-AllInOne:~/devstack$ docker version
Client:
 Version: 1.8.2
 API version: 1.20
 Go version: go1.4.2
 Git commit: 0a8c2e3
 Built: Thu Sep 10 19:19:00 UTC 2015
 OS/Arch: linux/amd64

Server:
 Version: 1.8.2
 API version: 1.20
 Go version: go1.4.2
 Git commit: 0a8c2e3
 Built: Thu Sep 10 19:19:00 UTC 2015
 OS/Arch: linux/amd64

stack@Steve-Magnum-AllInOne:~/devstack$ ssh fedora@172.24.4.4
The authenticity of host '172.24.4.4 (172.24.4.4)' can't be established.
ECDSA key fingerprint is 5e:10:c4:69:db:bb:fe:ab:5b:8d:04:ac:b3:39:58:e2.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.24.4.4' (ECDSA) to the list of known hosts.
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$ docker ps
Get http:///var/run/docker.sock/v1.19/containers/json: dial unix /var/run/docker.sock: permission denied. Are you trying to connect to a TLS-enabled daemon without TLS?
[fedora@swarmbay-jf2m3wlc2jem-swarm-master-oikqqxyccjo2 ~]$ sudo -i
-bash-4.3# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
-bash-4.3#
-bash-4.3# docker version
Client version: 1.7.1.fc21
Client API version: 1.19
Package Version (client): docker-io-1.7.1-2.git33de319.fc21.x86_64
Go version (client): go1.4.2
Git commit (client): 33de319/1.7.1
OS/Arch (client): linux/amd64
Server version: 1.7.1.fc21
Server API version: 1.19
Package Version (server): docker-io-1.7.1-2.git33de319.fc21.x86_64
Go version (server): go1.4.2
Git commit (server): 33de319/1.7.1
OS/Arch (server): linux/amd64