Failed to start any docker instance on atomic-5 image
Bug #1499607 reported by
Eli Qiao
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Use atomic-5 image to start a swarm bay.
can not start swarm-manager and swam-node service
http://
Changed in magnum: | |
assignee: | Eli Qiao (taget-9) → nobody |
Changed in magnum: | |
milestone: | none → mitaka-1 |
To post a comment you must log in.
[fedora@ swarmbay5- dxjbycmlbxig- swarm-master- ehfcg6hpsq6q ~]$ sudo docker version io-1.7. 1-2.git33de319. fc21.x86_ 64 io-1.7. 1-2.git33de319. fc21.x86_ 64
Client version: 1.7.1.fc21
Client API version: 1.19
Package Version (client): docker-
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-
Go version (server): go1.4.2
Git commit (server): 33de319/1.7.1
OS/Arch (server): linux/amd64
Google found that others have same issue with docker 1.7.1 /forums. docker. com/t/cannot- manage- containers- are-you- trying- to-connect- to-a-tls- enabled- daemon- without- tls/2144
https:/