Require upstream fix to runc to eliminate docker.d message flood
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu on IBM z Systems |
Fix Released
|
Medium
|
Skipper Bug Screeners | ||
| runc (Ubuntu) |
Fix Released
|
Undecided
|
Canonical Server | ||
| Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
| Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
Fix Released
|
Undecided
|
Canonical Server | ||
Bug Description
Problem Description:
Require upstream fix to runc to eliminate docker.d warning message flood
---uname output---
Linux zCX 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:19:08 UTC 2019 s390x s390x s390x GNU/Linux
Machine Type = s390x
---Debugger---
A debugger is not configured
---Steps to Reproduce---
zOS Container Extensions (zCX) customer reports log flooded with
msg="failed to retrieve runc version: unknown output format: runc version spec: 1.0.1-dev\n" messages.
zCX running on SSC 3.7.1 which is Ubuntu 18.04 s390x including
docker.io 18.09.7-
runc 1.0.0~rc7+
This problem matches debian.org bug report
https:/
In a test environment, downloaded
https:/
runc 1.0.0~rc6+dfsg1-3
and it does fix the problem.
Userspace tool common name: runc
Userspace rpm: runc
The userspace tool has the following bit modes: 64-bit
Userspace tool obtained from project website: Ubuntu 18.04 (Bionic) s390x
| tags: | added: architecture-s39064 bugnameltc-184001 severity-medium targetmilestone-inin--- |
| Changed in ubuntu: | |
| assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
| affects: | ubuntu → linux (Ubuntu) |
| tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin--- |
| affects: | linux (Ubuntu) → runc (Ubuntu) |
| Changed in ubuntu-z-systems: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
| Changed in runc (Ubuntu): | |
| assignee: | Skipper Bug Screeners (skipper-screen-team) → Canonical Server Team (canonical-server) |
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #2 |
| Changed in runc (Ubuntu Focal): | |
| status: | New → Fix Released |
| Changed in runc (Ubuntu Eoan): | |
| status: | New → Fix Committed |
| Changed in runc (Ubuntu Bionic): | |
| status: | New → Fix Committed |
| Changed in ubuntu-z-systems: | |
| status: | Triaged → Fix Committed |
| Frank Heimes (fheimes) wrote | #3 |
| Changed in runc (Ubuntu Eoan): | |
| status: | Fix Committed → Fix Released |
| Changed in runc (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
| Changed in ubuntu-z-systems: | |
| status: | Fix Committed → Fix Released |
| bugproxy (bugproxy) wrote | #4 |
As it happens I uploaded 1.0.0-rc10 to bionic UNAPPROVED a few days ago, which should fix this. I'll try to remember to update this bug when that gets into proposed.