Deeply layered Docker image problems
Bug #1702979 reported by
Edward Vielmetti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Michael Hudson-Doyle |
Bug Description
Docker 1.12.x is built with a version of Go which contains a bug (https:/
If Go (golang) is fixed to correct this bug then Docker builds cleanly.
If not, then you get mysterious behavior like this experience:
https:/
https:/
for which the only reasonable workaround now is to recommend to not use the system Docker but instead to get the latest-
tags: | added: id-59655279753fb7ac84fe2084 |
Changed in docker.io (Ubuntu): | |
status: | Triaged → Opinion |
status: | Opinion → Invalid |
Changed in docker.io (Ubuntu Xenial): | |
status: | New → Triaged |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
To post a comment you must log in.
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.