upgrade to 17.03.2-ce in 16.04+

Bug #1732368 reported by Michael Hudson-Doyle on 2017-11-15
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Undecided
Michael Hudson-Doyle
Xenial
Undecided
Michael Hudson-Doyle
Zesty
Undecided
Michael Hudson-Doyle
Artful
Undecided
Michael Hudson-Doyle

Bug Description

[Impact]
docker 17.03 came out over six months ago so we should clearly be at least that up to date...

[Test Case]
The autopkgtests per https://wiki.ubuntu.com/DockerUpdates. They should run on arm64 and s390x now in the scalingstack infrastructure but if they don't I'll run them by hand.

[Regression potential]
https://wiki.ubuntu.com/DockerUpdates again.

summary: - upgrade to 17.03.2-ce in all supported releases
+ upgrade to 17.03.2-ce in 16.04
summary: - upgrade to 17.03.2-ce in 16.04
+ upgrade to 17.03.2-ce in 16.04+
Changed in docker.io (Ubuntu):
status: New → Fix Released
Changed in docker.io (Ubuntu Xenial):
status: New → Triaged
Changed in docker.io (Ubuntu Zesty):
status: New → In Progress
status: In Progress → Triaged
Changed in docker.io (Ubuntu Artful):
status: New → Triaged
Changed in docker.io (Ubuntu Xenial):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in docker.io (Ubuntu Zesty):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in docker.io (Ubuntu Artful):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in docker.io (Ubuntu):
assignee: nobody → Michael Hudson-Doyle (mwhudson)
Changed in docker.io (Ubuntu Xenial):
status: Triaged → In Progress
Changed in docker.io (Ubuntu Zesty):
status: Triaged → In Progress
Changed in docker.io (Ubuntu Artful):
status: Triaged → In Progress

Hello Michael, or anyone else affected,

Accepted docker.io into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/17.03.2-0ubuntu1~17.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in docker.io (Ubuntu Artful):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-artful
Brian Murray (brian-murray) wrote :

Hello Michael, or anyone else affected,

Accepted docker.io into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/17.03.2-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in docker.io (Ubuntu Zesty):
status: In Progress → Fix Committed
tags: added: verification-needed-zesty
Brian Murray (brian-murray) wrote :

Hello Michael, or anyone else affected,

Accepted docker.io into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/17.03.2-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in docker.io (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed-xenial
George Kraft (cynerva) wrote :

This fails for me on xenial after upgrading from Docker v1.13.1 to 17.03.2-ce from xenial-proposed. Here's what I did:

1. Deploy a Canonical Distribution of Kubernetes cluster (which deploys worker instances with Xenial and gets Docker v1.13.1 via `apt install docker.io`)
2. On all worker units: add xenial-proposed line to sources.list.d, then `apt update && apt install docker.io`
3. Run `docker --version` on the worker units to confirm 17.03.2-ce was installed.

At this point, I observed that Kubernetes could no longer create containers, with errors coming from Docker along these lines:

Create container failed with error: invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:334: running prestart hook 0 caused \\\\\\\"fork/exec /usr/bin/dockerd (deleted): no such file or directory\\\\\\\"\\\"\\n\"

After observing this failure repeating for several minutes, I did the following:

4. On all worker units: `service docker restart`

This fixed the problem: the fork/exec errors from Docker stopped, and Kubernetes was able to create containers again.

George Kraft (cynerva) wrote :

Attached docker service logs where the fork/exec error can be seen. Some important times to consider:

~14:11:58 - docker v1.13.1 service starts
~14:36:00 - `apt install docker.io` upgrades docker to 17.03.2
~14:39:26 - Kubernetes starts trying to create new containers, fails
~14:52:18 - `service docker restart` - service restarts, fork/exec errors stop

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers