Docker latest=true displays transient failure

Bug #1445995 reported by Charles Butler
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
docker (Juju Charms Collection)
Fix Released
Critical
Charles Butler

Bug Description

When installing docker with the charm, and setting latest=true it causes intermittent failure

http://pastebin.ubuntu.com/10852805/

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.

Tags: papercut
Revision history for this message
Antonio Rosales (arosales) wrote :

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

Changed in docker (Juju Charms Collection):
status: Confirmed → In Progress
Revision history for this message
Charles Butler (lazypower) wrote :

This appears to be manifesting when docker is related to flannel-docker, and the template is rendering as invalid.

Investigation continues....

Changed in docker (Juju Charms Collection):
status: In Progress → Fix Released
Revision history for this message
Charles Butler (lazypower) wrote :

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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.