[Bug 1567096] [NEW] Docker doesn't work since Containerd integration

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

-- Problem Description --
Docker build hangs indefinitely when run using a 1.11.0 binary built after containerd integration, and go 1.6 on ppc64le. Doing the same thing works with gccgo.

Looking at the differences in docker logs shows that the containerd
event "exit", never happens when using a binary built with gc. fsnotify,
the file system handler for go, doesn't seem to receive the correct
event when a file is either written to, or closed, which I believe is
whats causing this issue.

Link to fsnotify issue which shows some failing tests :
https://github.com/fsnotify/fsnotify/issues/130

I have a patch that fixes the errors when I run fsnotify.  I am
preparing it for submission now and should be out there as a golang CL
this morning.

Do you want the patch so you can rebuild golang with it?  If fsnotify is
a separate package then you will have to rebuild it with the new golang.

Here's the CL link if you want to get the patch for ppc64le:  https://go-review.googlesource.com/#/c/21582/
Go to the upper right where it says download and I think if you select patch file it will give you the patch.

We'll update with more info after testing the patch Lynn submitted, but
we wanted to let Canonical know about this issue in the meantime since
1.11 is about to GA upstream.

** Affects: golang (Ubuntu)
     Importance: Undecided
     Assignee: Taco Screen team (taco-screen-team)
         Status: New


** Tags: architecture-ppc64le bugnameltc-139981 severity-critical targetmilestone-inin---
-- 
Docker doesn't work since Containerd integration
https://bugs.launchpad.net/bugs/1567096
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to golang in Ubuntu.