[16.10 FEAT] Upgrade Docker to newest version 1.12

[bugproxy]

Update Ubuntu 16.10 support for Docker 1.12. We want docker to be up to late in the current LTS.

See https://wiki.ubuntu.com/DockerUpdates

[Test Case]
autopkgtest + suite=xenial ./debian/docker-in-lxd as detailed in the wiki page. "docker version" reporting 1.12.1.

[Regression Poteinal]
See the wiki page linked above.

[Jon Grimm (jgrimm)]

Current plans are to update docker sometime after 1.12.1 is released upstream.

[Tianon Gravi (tianon)]

IMO it's also worth noting that 1.12.0 isn't GA yet -- upstream is still doing release candidates (currently at rc4), and the _current_ planned date for 1.12.0 is July 28th (although it used to be the 14th, so there's nothing to say it won't change again, especially if more issues manifest during the RCs).

[Dimitri John Ledkov (xnox)]

docker.io v1.12.0 is now GA

[Michael Hudson-Doyle (mwhudson)]

block-proposed because I want to test the "docker inside lxd" thing before this migrates.

[Dimitri John Ledkov (xnox)]

FTBFS on s390x in yakkety which is a supported architecture and therefore a blocker.

[Michael Hudson-Doyle (mwhudson)]

Yeah, Tianon has promised me a fix :-)

On 26 August 2016 at 12:52, Dimitri John Ledkov <email address hidden>
wrote:

> FTBFS on s390x in yakkety which is a supported architecture and
> therefore a blocker.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1602243
>
> Title:
> [16.10 FEAT] Upgrade Docker to newest version 1.12
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602243/+subscriptions
>

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-08-29 09:06 EDT-------
Canonical,

Is there still room to have Docker 1.12 for 16.10? I understand that packages do not upgrade often after feature freeze. Could docker be an exception here if we have the s390x fix?

[Jon Grimm (jgrimm)]

Hi Breno, Yes, 1.12 is still in-plan.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-09-01 12:25 EDT-------
Docker 1.12.1 is now available. Please integrate .... Thx

[Jon Grimm (jgrimm)]

Its in yakkety proposed, so on its way. :)

docker.io | 1.12.1-0ubuntu3 | yakkety-proposed/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x

[Michael Hudson-Doyle (mwhudson)]

My attempt at writing an autopkgtest for the docker-in-lxd thing mostly failed, but I've tested it by hand now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 1.12.1-0ubuntu7

---------------
docker.io (1.12.1-0ubuntu7) yakkety; urgency=medium

  * d/tests/control: disable docker-in-lxd again, does not work in production
    infrastructure.

 -- Michael Hudson-Doyle <email address hidden> Thu, 08 Sep 2016 09:41:13 +1200

[Brian Murray (brian-murray)]

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

[Chris J Arges (arges)]

Hello bugproxy, or anyone else affected,

Accepted runc into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/runc/1.0.0~rc1-0ubuntu1~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Chris J Arges (arges)]

Hello bugproxy, or anyone else affected,

Accepted containerd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd/0.2.3-0ubuntu1~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Chris J Arges (arges)]

Hello bugproxy, 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/1.12.1-0ubuntu7~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Michael Hudson-Doyle (mwhudson)]

Docker fails to start when the package from xenial-proposed is installed. The docker.socket unit is enabled but does not start.

The package in yakkety works and is very similar, so I think this is probably a bug in something in yakkety (maybe init-system-helpers?) but something needs fixing in any case.

[Michael Hudson-Doyle (mwhudson)]

I've uploaded a new package to the Xenial queue, which fixes that problem and for a bonus runs the docker-in-lxd test as part of its autopkgtest.

[Cindy Lee (cwsolee)]

Hi Micheal, My user and I notice the same problem on 16.04 too. When will the fix be available and looks like docker will also be upgraded to 1.12 when we've this fix?

[Kiran Mantripragada (kiran.mantri)]

updated to 1.12, but still having fatar error when running docker daemon / docker cli.

steps:
- sources.list updated (with the repository xenial-proposed)
- apt-get update
- apt-get install docker.io

(installation fails after trying to start the docker daemon service, but the binaries are installed)

--------

# dpkg -l | grep -e container -e runc
ii containerd 0.2.3-0ubuntu1~16.04 s390x daemon to control runC
iF docker.io 1.12.1-0ubuntu7~16.04 s390x Linux container runtime
ii runc 1.0.0~rc1-0ubuntu1~16.04 s390x Open Container Project - runtime

---------

# docker daemon
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x2aa0231ed26]

goroutine 1 [running]:
panic(0x2aa025b7500, 0xc82000e0c0)
 /usr/lib/go-1.6/src/runtime/panic.go:481 +0x400
crypto/aes.hasAsm()
 /usr/lib/go-1.6/src/crypto/aes/asm_s390x.s:25 +0x46

-------

# systemctl status docker.service
* docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2016-09-22 12:45:14 EDT; 5s ago
     Docs: https://docs.docker.com
  Process: 40151 ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=2)
 Main PID: 40151 (code=exited, status=2)

Sep 22 12:45:14 platcon2 dockerd[40151]: [signal 0xb code=0x1 addr=0x0 pc=0x2aa39470076]
Sep 22 12:45:14 platcon2 dockerd[40151]: goroutine 1 [running]:
Sep 22 12:45:14 platcon2 dockerd[40151]: panic(0x2aa3a8967a0, 0xc82000e090)
Sep 22 12:45:14 platcon2 dockerd[40151]: /usr/lib/go-1.6/src/runtime/panic.go:481 +0x400
Sep 22 12:45:14 platcon2 dockerd[40151]: crypto/aes.hasAsm()
Sep 22 12:45:14 platcon2 dockerd[40151]: /usr/lib/go-1.6/src/crypto/aes/asm_s390x.s:25 +0x46
Sep 22 12:45:14 platcon2 systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 22 12:45:14 platcon2 systemd[1]: Failed to start Docker Application Container Engine.
Sep 22 12:45:14 platcon2 systemd[1]: docker.service: Unit entered failed state.
Sep 22 12:45:14 platcon2 systemd[1]: docker.service: Failed with result 'exit-code'.

------

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

------

# uname -a
Linux platcon2 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:19:48 UTC 2016 s390x s390x s390x GNU/Linux

[Michael Hudson-Doyle (mwhudson)]

Hm, that's exciting :( I can't reproduce it on the instance I have access to, but that's Yakkety. It really shouldn't make a difference, but I'll work to rule it out. The other question is what architecture/facilities your node has.

[Steve Langasek (vorlon)]

Hello bugproxy, 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/1.12.1-0ubuntu12~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Steve Langasek (vorlon)]

Hello bugproxy, 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/1.12.1-0ubuntu12~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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Steve Langasek (vorlon)]

Hello bugproxy, 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/1.12.1-0ubuntu13~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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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!

[Michael Hudson-Doyle (mwhudson)]

I've run the autopkgtests on arm64/xenial by hand, looks good so far.

[Michael Hudson-Doyle (mwhudson)]

Finally got hold of an s390x/xenial system to test and it passed there, so let's call that done.

[Launchpad Janitor (janitor)]

This bug was fixed in the package containerd - 0.2.3-0ubuntu1~16.04

---------------
containerd (0.2.3-0ubuntu1~16.04) xenial; urgency=medium

  * Backport to Xenial. (LP: #1602243)

 -- Michael Hudson-Doyle <email address hidden> Thu, 08 Sep 2016 23:19:43 +1200

[Martin Pitt (pitti)]

The verification of the Stable Release Update for containerd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package docker.io - 1.12.1-0ubuntu13~16.04.1

---------------
docker.io (1.12.1-0ubuntu13~16.04.1) xenial; urgency=medium

  * Backport to Xenial. (LP: #1602243)
  * d/control: Remove version from Build-Depends on dh-golang, only
    required in Debian.
  * Install the service file with .install again, fixing service activation
    on install.

 -- Michael Hudson-Doyle <email address hidden> Tue, 27 Sep 2016 12:25:38 +1300

[Launchpad Janitor (janitor)]

This bug was fixed in the package runc - 1.0.0~rc1-0ubuntu1~16.04

---------------
runc (1.0.0~rc1-0ubuntu1~16.04) xenial; urgency=medium

  * Backport to Xenial. (LP: #1602243)

 -- Michael Hudson-Doyle <email address hidden> Thu, 08 Sep 2016 23:21:15 +1200