Docker latest=true displays transient failure
Bug #1445995 reported by
Charles Butler
on 2015-04-19
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | docker (Juju Charms Collection) |
Critical
|
Charles Butler | ||
Bug Description
When installing docker with the charm, and setting latest=true it causes intermittent failure
http://
The byproduct of this results in a docker binary that is unable to perform any operations. The only known solution to date is to reboot the node, which is not ideal.
| Antonio Rosales (arosales) wrote : | #1 |
Charles Butler (lazypower)
on 2015-04-19
| Changed in docker (Juju Charms Collection): | |
| status: | Confirmed → In Progress |
| Charles Butler (lazypower) wrote : | #2 |
This appears to be manifesting when docker is related to flannel-docker, and the template is rendering as invalid.
Investigation continues....
Charles Butler (lazypower)
on 2015-05-07
| Changed in docker (Juju Charms Collection): | |
| status: | In Progress → Fix Released |
| Charles Butler (lazypower) wrote : | #3 |
Correct resolution was to guard and gate against empty config. The dockerfile was being rewritten in a race condition with no data, then not being updated after the fact. Cycling of the docker daemon with an invalid --DOCKER_OPTS was the culprit.
To post a comment you must log in.
I have been able to reproduce this in EC2 and Azure. The current workaround given by Chuck is to remove the Docker config option of "latest=true" in the bundle and take the charm default of false. Doing so allows unit 0 and 1 of the Docker charm to be deployed.
-thanks,
Antonio