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

Reply via email to