This bug was fixed in the package runc - 1.0.0~rc95-0ubuntu1~18.04.1
---
runc (1.0.0~rc95-0ubuntu1~18.04.1) bionic; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by upstream and fixed in
this new release.
+ Ensure the scratch
This bug was fixed in the package runc - 1.0.0~rc95-0ubuntu1~20.04.1
---
runc (1.0.0~rc95-0ubuntu1~20.04.1) focal; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by upstream and fixed in
this new release.
+ Ensure the scratch
This bug was fixed in the package runc - 1.0.0~rc95-0ubuntu1~21.04.1
---
runc (1.0.0~rc95-0ubuntu1~21.04.1) hirsute; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by upstream and fixed in
this new release.
+ Ensure the scratch
This bug was fixed in the package runc - 1.0.0~rc95-0ubuntu1~20.10.1
---
runc (1.0.0~rc95-0ubuntu1~20.10.1) groovy; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by upstream and fixed in
this new release.
+ Ensure the scratch
I did the verification of the packages in -proposed in all releases:
Hirsute
---
ubuntu@hirsute:~/runc/runc-1.0.0-rc95$ head -n 12 debian/changelog
runc (1.0.0~rc95-0ubuntu1~21.04.1) hirsute; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by
Regarding the golang-github-containers-common/0.33.4+ds1-1 regression in
Hirsute, it was reported here in LP #1931258 as a LTO optimization
issue. We could SRU this package adding the
export DEB_BUILD_MAINT_OPTIONS=optimize=-lto
to d/rules but I believe this does not worth a SRU. If the SRU team
The containerd regressions in Focal and Bionic were already sorted out,
the tests are passing now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in
I've been trying to find a fix for the golang-github-containers-
common/0.33.4+ds1-1 regression in Hirsute but without success so far.
However, the issue seems to be unrelated to this runc SRU, it is a
compilation issue in one of its components:
# github.com/containers/storage/pkg/devicemapper
I confirmed the golang-github-docker-go-connections regression in
Hirsute and I filed another SRU bug to fix it:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-
connections/+bug/1930891
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Brian,
I tested the package from focal-proposed and everything is working as
expected.
Tested version:
root@node0:~# runc -v
runc version 1.0.0~rc95-0ubuntu1~20.04.1
spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1
Test:
Start 300 replicas of nginx on a single kuberentes node.
** Tags
Hello Colin, or anyone else affected,
Accepted runc into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/runc/1.0.0~rc95-0ubuntu1~20.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Colin, or anyone else affected,
Accepted runc into hirsute-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/runc/1.0.0~rc95-0ubuntu1~21.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package runc - 1.0.0~rc95-0ubuntu1
---
runc (1.0.0~rc95-0ubuntu1) impish; urgency=medium
* New upstream release.
- Several regressions were found in 1.0.0-rc93 by upstream and fixed in
this new release.
+ Ensure the scratch pipe is read
** Changed in: runc (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: runc (Ubuntu Focal)
Importance: Undecided => High
** Changed in: runc (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: runc (Ubuntu Hirsute)
Importance: Undecided => High
--
You received
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in containerd with latest runc
version
To manage notifications about this bug
Thanks for the testing Colin!
FYI I already uploaded the fix to Impish (development release) and as
soon it lands in the release pocket I can start the SRUs. At the moment
it is blocked by one regression:
https://people.canonical.com/~ubuntu-archive/proposed-
@Lucas, I just tested with runc 1.0.0~rc95-0ubuntu1~20.04.1~ppa1 from
your PPA, everything is working ok (300 containers tested).
I don't know if the containerd update is planned, but I ran the test
with containerd 1.3.3-0ubuntu2.3 from the Ubuntu repo and
1.5.2-0ubuntu1~20.04.1~ppa1 form your
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: runc (Ubuntu Hirsute)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: runc (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: runc (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: runc (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
As Colin stated, this version of runc is causing a serious regression.
As such it should be marked as High.
** Changed in: runc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219
Title:
context deadline exceeded: unknown in containerd with latest runc
version
To manage notifications about this bug
** Changed in: runc (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Groovy)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
**
** Description changed:
+ [Impact]
+
+ Several regressions were identified by upstream in version 1.0.0-rc93
+ and were fixed in version 1.0.0-rc94:
+
+ https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc94
+
+ "This release fixes several regressions found in v1.0.0-rc93. We
+
** Also affects: runc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Focal)
@Colin I updated my PPA with version 1.0-rc95 which also contains the
fix for CVE-2021-30465. Could you test this new version and make sure
your regression is fixed?
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30465
--
You received this bug notification because you are a
I'm marking this bug as Triaged: I didn't try to reproduce it locally,
but I think it's clear enough we have a bug here. Also tagging this as a
regression.
** Changed in: runc (Ubuntu)
Status: Incomplete => Triaged
** Tags added: regression-update server-next
--
You received this bug
Thanks for raising this issue. The VERSION file is not missing but we
are not using the upstream Makefile to build the source, that's why the
version is not set.
I fixed this issue and uploaded the fix to my PPA (it might take some
minutes to get it published), now if you update the runc package
The missing version seems to be caused by a different build environment
(missing VERSION file at the root of the source tree).
https://github.com/opencontainers/runc/blob/master/main.go#L20
https://github.com/opencontainers/runc/blob/master/Makefile#L15
--
You received this bug notification
The version published in the PPA fixes the issue.
```
root@node0:~# runc -v
runc version spec: 1.0.2-dev
go: go1.13.8
libseccomp: 2.5.1
```
Fore some reason, the runc version published in the PPA don't show the actual
runc version with `runc -v`, just like the previous version (1.0-rc93)
I updated the runc package to version 1.0-rc94 and it is available in
this PPA for testing:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-stack
Let me know if this indeed fix your issue. If yes, I'll update runc in
the development release (a.k.a. impish) and then start the SRU
Of course, I could try a PPA or an attached deb file, anything that suits you
best, everything is running on a test system anyway.
Thanks for your help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the investigation! It seems that a bunch of regressions were
found in 1.0.0~rc93 as we can see in the 1.0.0~rc94 release notes:
"This release fixes several regressions found in v1.0.0-rc93. We
recommend users update as soon as possible."
I tested the pre-built binary of the latest version of runc (by just replacing
/usr/sbin/runc) and I was able to go to 400 pods on a single test node.
This new version was released today.
```
root@node0:~# runc -v
runc version 1.0.0-rc94
spec: 1.0.2-dev
go: go1.14.15
libseccomp: 2.5.1
```
In order to test weave's container network impact, on the limit, I
started 200 "sleep 7200" pods with the busybox image, with "hostNetwork:
true" to disable container networking.
This time, I was able to run 200 replicas, but I was unable to go to
over 200 pods, I tried the grow the replicas
I was able to reproduce the behaviour under a test VM.
I used a simple example nginx deployment with a high number of replicas.
With the older version of runc, I was able to run 200 replicas
successfully and even 250.
With the newer version of runc, I was only able to run 164 replicas out of
Hi,
Here is the kern.log extract of the time containers were trying to start.
I only see logs about network interfaces, and the log is full of it.
I don't see those logs anymore after the runc version downgrade.
It looks like just a consequence of the runner's start failure.
About the load, I
Hello and thanks for this bug report. I had a look a the runc bug
reports and changes to see if I could easily spot a relevant change, but
I couldn't. I don't have a good hypothesis of what could be wrong, but
I'd start checking if the newer runc is causing a higher memory or CPU
usage, causing
39 matches
Mail list logo
