[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-14 Thread Launchpad Bug Tracker
This bug was fixed in the package docker.io - 1.13.1-0ubuntu1~16.04.2

---
docker.io (1.13.1-0ubuntu1~16.04.2) xenial; urgency=medium

  * Rebuild with golang-1.6 1.6.2-0ubuntu5~16.04.4 which uses the correct page
size on arm64 for use with Ubuntu kernels. (LP: #1702979)

docker.io (1.13.1-0ubuntu1~16.04.1) xenial; urgency=medium

  * Backport to Xenial. (LP: #1712954)
  * Install the service file with .install again, fixing service activation
on install.
  * Use golang.org/x/net/context instead of stdlib context to enable building
with Go 1.6.

 -- Michael Hudson-Doyle   Thu, 02 Nov 2017
11:43:13 +1300

** Changed in: docker.io (Ubuntu Xenial)
   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/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-05 Thread Michael Hudson-Doyle
Actually I wanted to check some things for myself so I installed a
system, installed the version of docker.io 1.13 that was in proposed
before this bug was fixed, verified that the 'deep-files' build failed
(thanks for the super simple test case!) in the same way as you
described, then installed 1.13.1-0ubuntu1~16.04.2 and verified that the
build succeeded. I also ran the basic arm64 smoke tests but I'd still be
interested in the results of any testing you can do.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1702979] Re: Deeply layered Docker image problems

2017-11-05 Thread Michael Hudson-Doyle
On 3 November 2017 at 15:27, Edward Vielmetti 
wrote:

> Michael - I'm able to test this, but I need to set up a fresh machine to
> make sure I didn't bodge one of the install steps.
>

Thanks.


> Just to be clear, the xenial-proposed version is 1.13.1 based, and the
> earlier PPA version was 1.12.x based, so this is newer code than what I
> had first tested.
>

Yes, that's a good point. I'd be interesting in hearing about any
regressions that are caused by the newer version! (We don't have any
autopkgtests running on arm64 yet unfortunately).

We'll be moving on to 17.03.2-ce at some point not too far away
hopefully.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-02 Thread Edward Vielmetti
Michael - I'm able to test this, but I need to set up a fresh machine to
make sure I didn't bodge one of the install steps.

Just to be clear, the xenial-proposed version is 1.13.1 based, and the
earlier PPA version was 1.12.x based, so this is newer code than what I
had first tested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-02 Thread Michael Hudson-Doyle
Hi Ed, are you able to test the version of docker.io that's now in
xenial-proposed? If not, I can do it but it's always best to get the
original reporter to check that problems are fixed!

This version can't be released to updates until the k8s people release
their charms (see #1712954) but I think that's due today or tomorrow.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-01 Thread Adam Conrad
Hello Edward, 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.13.1-0ubuntu1~16.04.2
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: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-01 Thread Michael Hudson-Doyle
** Also affects: docker.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: docker.io (Ubuntu)
   Status: Triaged => Opinion

** Changed in: docker.io (Ubuntu)
   Status: Opinion => Invalid

** Changed in: docker.io (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: docker.io (Ubuntu Xenial)
 Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-11-01 Thread Edward Vielmetti
I've confirmed that the PPA provided by @mwhudson in #4 addresses the
crash reported in the issue.

I've also identified a simple test Dockerfile that crashes on an
unpatched system, and works properly on the new PPA.

https://gist.github.com/bdafb8e961f55b2533fee8fa5221d186 - rename as
"Dockerfile", then run

$ docker build -t deep-files .

With the PPA, this runs to completion; without it, it crashes at build
time with

Step 41 : RUN mkdir 40
error creating aufs mount to /var/lib/docker/aufs/mnt/787c80e88d99c4ed74305f16ce
30395e3346cfa4629c3d078f9fab3c6e4e52f0: invalid argument

The Dockerfile is very simple; it just creates 100 directories, one
layer at a time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-09-29 Thread Francis Ginther
** Tags added: id-59655279753fb7ac84fe2084

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702979] Re: Deeply layered Docker image problems

2017-08-21 Thread Edward Vielmetti
Hi @rkota - I was able to successfully install this version of Docker
from the PPA.

I'm working on a test setup that generates enough layers to prove out
the bug, and will report back when I get that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-08-10 Thread Raghuram Kota
Hi @Edward Vielmetti : Trying to follow up to see if you had a chance to
test.  Many thanks for the help!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1702979] Re: Deeply layered Docker image problems

2017-07-31 Thread Edward Vielmetti
Thanks Raghuram - I'll put together a test based on the PPA.

On Mon, Jul 31, 2017 at 10:32 AM, Raghuram Kota  wrote:

> Hi @Edward Vielmetti : Would it be possible for you to test the fix
> uploaded to PPA by mwhudson (comm # 4 ?) ? Thx!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1702979
>
> Title:
>   Deeply layered Docker image problems
>
> Status in docker.io package in Ubuntu:
>   Triaged
>
> Bug description:
>   Docker 1.12.x is built with a version of Go which contains a bug
>   (https://bugs.launchpad.net/ubuntu/+source/golang-
>   defaults/+bug/1661222) in syscall.Getpagesize. As a result, Docker
>   builds that create images with lots of layers fail to behave properly.
>
>   If Go (golang) is fixed to correct this bug then Docker builds
>   cleanly.
>
>   If not, then you get mysterious behavior like this experience:
>
>   https://github.com/ros2/ci/pull/73
>   https://github.com/ros2/ci/issues/75
>
>   for which the only reasonable workaround now is to recommend to not
>   use the system Docker but instead to get the latest-and-greatest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/
> 1702979/+subscriptions
>


-- 
Edward Vielmetti +1 734 330 2465
edward.vielme...@gmail.com

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-31 Thread Raghuram Kota
Hi @Edward Vielmetti : Would it be possible for you to test the fix
uploaded to PPA by mwhudson (comm # 4 ?) ? Thx!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-19 Thread Raghuram Kota
A build with option #1 suggested in comment #2 is now available in a PPA
(Many thanks to mwhudson!) and is ready for test. To install :

$ sudo add-apt-repository ppa:mwhudson/devirt
$ sudo apt-get update

Then apt-get upgrade or apt-get install docker.io containerd runc should
get the rebuilt versions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-17 Thread Edward Vielmetti
** Bug watch added: github.com/ros2/ci/issues #75
   https://github.com/ros2/ci/issues/75

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1702979] Re: Deeply layered Docker image problems

2017-07-17 Thread Edward Vielmetti
I can test this possible fix (repair Go, then rebuild Go) next week, I am
on holiday this week.

> 1) Use Adam's suggestion from bug 1661222 of patching Go to use the
actually-correct-on-all-Ubuntu page size, then rebuilding docker.

On Sun, Jul 16, 2017 at 9:11 PM, Michael Hudson-Doyle <
mwhudso...@fastmail.fm> wrote:

> Fixing the go bug in the version of Go in Xenial is highly non-trivial
> and I don't really want to go there. Two other ways of approaching this
> would be:
>
> 1) Use Adam's suggestion from bug 1661222 of patching Go to use the
> actually-correct-on-all-Ubuntu page size, then rebuilding docker.
>
> 2) Build docker with a newer version of Go. There is no newer version of
> Go in Xenial but we could in theory upload a newer version or build the
> newer version of Go as part of the docker build.
>
> 1) would be very very much easier, is it possible for you to test if
> this actually helps?
>
> Another option would be to steer your customers towards the docker snap,
> if that works better (I haven't tried it at all on arm64 but it does at
> least seem to be built there).
>
> ** Changed in: docker.io (Ubuntu)
>Status: New => Triaged
>
> ** Changed in: docker.io (Ubuntu)
>Importance: Undecided => High
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1702979
>
> Title:
>   Deeply layered Docker image problems
>
> Status in docker.io package in Ubuntu:
>   Triaged
>
> Bug description:
>   Docker 1.12.x is built with a version of Go which contains a bug
>   (https://bugs.launchpad.net/ubuntu/+source/golang-
>   defaults/+bug/1661222) in syscall.Getpagesize. As a result, Docker
>   builds that create images with lots of layers fail to behave properly.
>
>   If Go (golang) is fixed to correct this bug then Docker builds
>   cleanly.
>
>   If not, then you get mysterious behavior like this experience:
>
>   https://github.com/ros2/ci/pull/73
>   https://github.com/ros2/ci/issues/75
>
>   for which the only reasonable workaround now is to recommend to not
>   use the system Docker but instead to get the latest-and-greatest.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/
> 1702979/+subscriptions
>


-- 
Edward Vielmetti +1 734 330 2465
edward.vielme...@gmail.com

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-16 Thread Michael Hudson-Doyle
Fixing the go bug in the version of Go in Xenial is highly non-trivial
and I don't really want to go there. Two other ways of approaching this
would be:

1) Use Adam's suggestion from bug 1661222 of patching Go to use the
actually-correct-on-all-Ubuntu page size, then rebuilding docker.

2) Build docker with a newer version of Go. There is no newer version of
Go in Xenial but we could in theory upload a newer version or build the
newer version of Go as part of the docker build.

1) would be very very much easier, is it possible for you to test if
this actually helps?

Another option would be to steer your customers towards the docker snap,
if that works better (I haven't tried it at all on arm64 but it does at
least seem to be built there).

** Changed in: docker.io (Ubuntu)
   Status: New => Triaged

** Changed in: docker.io (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702979] Re: Deeply layered Docker image problems

2017-07-13 Thread Edward Vielmetti
We've seen a second customer using ARM64 Docker 1.12.6 on Ubuntu running
into errors that could be explained by issue. Would it be possible to
triage it? Fixing the upstream Go bug and recompiling may be enough to
solve.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702979

Title:
  Deeply layered Docker image problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1702979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs