-
Notifications
You must be signed in to change notification settings - Fork 50
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
docker 24.0.9, runc 1.1.12, containerd 1.7.13 for beta #1628
Conversation
It's from Gentoo commit 71e59e7b073056573e741231c09811914bd8c7e0.
It's from Gentoo commit fbea8bb95ebcf0209859298e699056bf60fa8c6b.
It's from Gentoo commit 76215ae8b1d05aaaa3ac1c73eb25fe9db7e612d9.
Thanks! |
Build action triggered: https://github.com/flatcar/scripts/actions/runs/7821201809 |
Yeah, we could move it to portage-stable now. We could also drop app-containers/docker-proxy from portage-stable as it is not pulled in any more. |
Any clue what the failure in |
Looks unrelated because it downloads something from bincache instead of an artifact of this PR
|
Maybe the |
Alright, I'll ignore it for now. Kicked off the CI again, because containerd insisted on pulling in the old version of runc. Same thing done for alpha and main. |
For a more simple approach to problems like this I would always delete the old ebuilds to prevent them from being used accidentally. |
That would fail the build, as containerd had a dependency on any revision of runc 1.1.9. Admittedly that would be more noticable than just looking at the image reports. |
changelog/
directory (user-facing change, bug fix, security fix, update)/boot
and/usr
size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.