-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v0.11 backport] Dockerfile: RUNC_VERSION=v1.1.5 #3763
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM do we want this in the 0.10 branch as well, or not worth the effort?
@thaJeztah Did you find out more about the error with container not starting in new runc because of mount validation(and possible fd switch)? Is this safe to pick? |
@tonistiigi you mean the rootless errors on the other PR? No. Must admit that I didn't dig into it, and was slightly hoping it would ring a bell for @AkihiroSuda |
@thaJeztah This one(copy from your message):
|
Oh! Nope, didn't find yet; but a colleague mentioned that they encountered that error occasionally in CI on that repo (we should probably look if we can track those failures as well) |
2ceb5e8
to
053777c
Compare
053777c
to
18455d7
Compare
Signed-off-by: Akihiro Suda <[email protected]> (cherry picked from commit 03b48a0) Signed-off-by: Akihiro Suda <[email protected]>
18455d7
to
ae5a76a
Compare
Rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -1,6 +1,6 @@ | |||
# syntax=docker/dockerfile-upstream:master | |||
|
|||
ARG RUNC_VERSION=v1.1.4 | |||
ARG RUNC_VERSION=v1.1.5 | |||
ARG CONTAINERD_VERSION=v1.6.18 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per the other thread; do we need containerd v1.6.20 as well, or best to do separately? (maybe separately is okay to not mix backports)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be done separately
Cherry-pick: