** Tags removed: verification-done
** Tags added: bugnameltc-143688 severity-medium verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to ne
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
To manag
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 Thu, 08 Sep 2016
23:21:15 +1200
--
You received this bug notification because you are a mem
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 ser
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 Thu, 08 Sep 2016
23:19:43 +1200
** Changed in: containerd (Ubuntu Xenial)
Status:
Finally got hold of an s390x/xenial system to test and it passed there,
so let's call that done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I've run the autopkgtests on arm64/xenial by hand, looks good so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
To manage notif
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
To manage notif
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
** Tags removed: bugnameltc-143688 severity-medium upgrade-software-
version verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest ve
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.
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.
--
You received this bug notification because you are a member o
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 inst
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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
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.
** Changed in: docker.io (Ubuntu Xenial)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of
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
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
To manage
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.
** Description changed:
- Update Ubuntu 16.10 support for Docker 1.12
+ 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
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
htt
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
To manage notif
** Changed in: containerd (Ubuntu Xenial)
Status: New => In Progress
** Changed in: docker.io (Ubuntu Xenial)
Status: New => In Progress
** Changed in: runc (Ubuntu Xenial)
Status: New => In Progress
** Changed in: containerd (Ubuntu Xenial)
Assignee: (unassigned) => Mi
** Changed in: runc (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: containerd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
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 Thu, 08 Sep 2016
09:41:13 +1200
** Chang
My attempt at writing an autopkgtest for the docker-in-lxd thing mostly
failed, but I've tested it by hand now.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
T
Its in yakkety proposed, so on its way. :)
docker.io | 1.12.1-0ubuntu3 | yakkety-proposed/universe |
source, amd64, arm64, armhf, i386, ppc64el, s390x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Hi Breno, Yes, 1.12 is still in-plan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
h
Yeah, Tianon has promised me a fix :-)
On 26 August 2016 at 12:52, Dimitri John Ledkov
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/160
FTBFS on s390x in yakkety which is a supported architecture and
therefore a blocker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEAT] Upgrade Docker to newest version 1.12
block-proposed because I want to test the "docker inside lxd" thing
before this migrates.
** Also affects: docker.io (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Michael
Hudson-Doyle (m
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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:
** Summary changed:
- [FEAT 16.10] Upgrade Docker to newest version 1.12
+ [16.10 FEAT] Upgrade Docker to newest version 1.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602243
Title:
[16.10 FEA
32 matches
Mail list logo