runc -v empty output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
runc (Ubuntu) |
Fix Released
|
Low
|
Lucas Kanashiro | ||
Bionic |
Fix Released
|
Undecided
|
Lucas Kanashiro | ||
Focal |
Fix Released
|
Undecided
|
Lucas Kanashiro | ||
Groovy |
Fix Released
|
Undecided
|
Lucas Kanashiro | ||
Hirsute |
Fix Released
|
Undecided
|
Lucas Kanashiro |
Bug Description
[Impact]
Users cannot check the runc version running 'runc --version'. This is not a big deal but it would land along with LP #1927219 which is an important fix.
[Test Plan]
Check if 'runc --version' returns the runc version.
[Where problems could occur]
As usual, we deliver most benefit to our users by delivering an upstream experience. A risk of regressions is part of that.
[Original Message]
Apparently runc is built in some non-standard way, so it does not show its version:
kir@ubu2004:~$ runc -v
runc version spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1
In the output above, version string is empty and there is no newline added, so we have a version of the spec in the same line. Thus, docker has the same problem reporting runc version:
kir@ubu2004:~$ docker version | grep -A2 runc
runc:
Version: spec: 1.0.2-dev
GitCommit:
For comparison, here is the correct/expected output:
[kir@kir-rhat runc]$ runc -v
runc version 1.0.0-rc93+dev
commit: ba257d2de86e7e5
spec: 1.0.2-dev
go: go1.15.8
libseccomp: 2.5.0
Package information:
kir@ubu2004:~$ dpkg -l runc
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii runc 1.0.0~rc93-
kir@ubu2004:~$ runc -v
runc version spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1
CVE References
affects: | linux (Ubuntu) → runc (Ubuntu) |
Changed in runc (Ubuntu): | |
status: | Incomplete → New |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1929106
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.