-
Notifications
You must be signed in to change notification settings - Fork 16
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
Debian: remove force-cgroups-v1 code #338
Conversation
Cirrus CI build successful. Found built image names and IDs:
|
Cirrus CI build successful. Found built image names and IDs:
|
[Packages are identical to #338] |
52e8fc2
to
9c2d6e8
Compare
Well, this is not going to be easy. |
Cirrus CI build successful. Found built image names and IDs:
|
9c2d6e8
to
7529bf0
Compare
Cirrus CI build successful. Found built image names and IDs:
|
|
As agreed in Planning meeting of 2024-03-20, Podman 5.x will drop support for cgroups v1 and for runc. Make it so. CI images built in containers/automation_images#338 Signed-off-by: Ed Santiago <santiago@redhat.com>
As agreed in Planning meeting of 2024-03-20, Podman 5.x will drop support for cgroups v1 and for runc. Make it so. CI images built in containers/automation_images#338 Signed-off-by: Ed Santiago <santiago@redhat.com>
7529bf0
to
b27b1a2
Compare
@containers/podman-maintainers looks like our days of testing cgroups v1 are numbered. New debian VMs are bringing in new systemd, which refuses to boot under cgroups v1. See #355 for further details. |
I think that's OK now. We don't release to RHEL8 anymore. 9 can switch to CGv1 but it's not the default. 5 officially deprecated CGv1 support. |
it's okay, and (per commit message) this was agreed to on March 20 in Planning, but podman tests are going to need some surgery and I've let that slide. Fortunately I have nothing else going on this week[1] so I'll get on that ASAP. [1] joke. not a funny one. |
Think of the all the v1/v2 conditionals that we can remove in the tests and eventually the code as well |
b27b1a2
to
3fdfa74
Compare
As agreed in Planning meeting of 2024-03-20, Podman 5.x will drop support for cgroups v1 and for runc. Make it so. CI images built in containers/automation_images#338 Signed-off-by: Ed Santiago <santiago@redhat.com>
Cirrus CI build successful. Found built image names and IDs:
|
As agreed in Planning meeting of 2024-03-20, Podman 5.x will drop support for cgroups v1 and for runc. Make it so. CI images built in containers/automation_images#338 Signed-off-by: Ed Santiago <santiago@redhat.com>
Per consent in 2024-03-20 Planning, remove support for cgroups v1. And, per discovery on 2024-05-28, systemd 256 no longer even boots on a cgroups v1 system. This commit switches to VMs built in: containers/automation_images#338 ...in which Debian is now cgroups v2 with crun. Signed-off-by: Ed Santiago <santiago@redhat.com>
Per consent in 2024-03-20 Planning, remove support for cgroups v1. And, per discovery on 2024-05-28, systemd 256 no longer even boots on a cgroups v1 system. This commit switches to VMs built in: containers/automation_images#338 ...in which Debian is now cgroups v2 with crun. Requires disabling two conformance tests which fail when run against docker 26.1; see containers#5526 for context on those. And, latest git on f40 refuses to serve non-root files when run as root ("dubious ownership"); so, in start_git_daemon(), chown the extracted files. Signed-off-by: Ed Santiago <santiago@redhat.com>
|
sigh..... |
Per discussion in 2024-03-20 Planning meeting, we will no longer be testing runc in CI. And cgroups V1 is dead too. Signed-off-by: Ed Santiago <santiago@redhat.com>
It has been retired in Rawhide, and it's unclear whether we need it at all. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
plocate is the default locate implementation in Fedora. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
3fdfa74
to
564b76c
Compare
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.
Thanks for taking care of this Ed.
> panic: encoding alphabet includes duplicate symbols Signed-off-by: Miloslav Trmač <mitr@redhat.com>
Cirrus CI build successful. Found built image names and IDs:
|
|
Per consent in 2024-03-20 Planning, remove support for cgroups v1. And, per discovery on 2024-05-28, systemd 256 no longer even boots on a cgroups v1 system. This commit switches to VMs built in: containers/automation_images#338 ...in which Debian is now cgroups v2 with crun. Requires disabling two conformance tests which fail when run against docker 26.1; see containers#5526 for context on those. Also requires disabling two bats tests on debian because something changed there in ulimits. I'll look into them later but right now this gives us breathing space. And, latest git on f40 refuses to serve non-root files when run as root ("dubious ownership"); so, in start_git_daemon(), chown the extracted files. Signed-off-by: Ed Santiago <santiago@redhat.com>
Per consent in 2024-03-20 Planning, remove support for cgroups v1. And, per discovery on 2024-05-28, systemd 256 no longer even boots on a cgroups v1 system. This commit switches to VMs built in: containers/automation_images#338 ...in which Debian is now cgroups v2 with crun. Requires disabling two conformance tests which fail when run against docker 26.1; see containers#5526 for context on those. Also requires disabling two bats tests on debian because something changed there in ulimits. I'll look into them later but right now this gives us breathing space. And, latest git on f40 refuses to serve non-root files when run as root ("dubious ownership"); so, in start_git_daemon(), chown the extracted files. Signed-off-by: Ed Santiago <santiago@redhat.com>
Another new-VM import from containers/automation_images#338 ...because the usual conflict dealio in that repo. This should mostly be a NOP. All the major work was done in containers#22706. Signed-off-by: Ed Santiago <santiago@redhat.com>
Changes: - fix from @mtrmac for go-1.22 panic ("alphabet, duplicate symbols") - debian is now cgroupsv2 + crun (does not affect skopeo) - many other Red Queen fixes Built in: containers/automation_images#338 Signed-off-by: Ed Santiago <santiago@redhat.com>
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, thanks for seeing this through. In my mind at least, there's a bunch of comments and code in podman CI that (when using these images) will confusingly suggest CGv1 is in use. Are there any "cgroupsv1" cleanup/followup issues or cards that need creating?
Thank you. Yes, there will be a ton of cleanup needed to remove special-case conditionals. I've chosen not to tackle that yet. |
That's fine, I or someone else may be able to help with this. I just wanted to know if you had already opened an issue/card or set a personal reminder. I'll go ahead and file a Jira card. |
Per discussion in 2024-03-20 Planning meeting, we will no
longer be testing runc in CI. And cgroups V1 is dead too.
Signed-off-by: Ed Santiago santiago@redhat.com