-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New VM images 2025-09-10 #27030
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
New VM images 2025-09-10 #27030
Conversation
debian images are broken with some for of keryring leak. I have seen this in fedora openQA before and it was tied to the systemd update there https://bodhi.fedoraproject.org/updates/FEDORA-2025-a0ce059969 which then was traced bug to a kernel bug AFAICT systemd/systemd#38724 |
containers/automation_images#416 Signed-off-by: Paul Holzinger <[email protected]>
[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore. |
The full error message is: failed to create idmapped mount: mount_setattr /tmp/CI_SKPI/podman_bats.RX6gD9/rootfs: invalid argument So in order to match this account for the variable part. Signed-off-by: Paul Holzinger <[email protected]>
On debian with an older we get this error instead: fsconfig() failed: tmpfs: Unknown parameter 'noswap' So handle that case as well to skip the test correctly. Signed-off-by: Paul Holzinger <[email protected]>
The ls call for the directory now fails with EACCES, see https://github.com/containers/crun/issues/1876 Signed-off-by: Paul Holzinger <[email protected]>
Note the debian images now use a 6.1 kernel instead to work around the memory leak on the 6.16 kernel that we hit otherwise. Thus I had to fix the skips for older kernels as they were not working properly. |
This also bring in go 1.24 so we can bump the repo here #27017 |
@timcoding1988 @containers/podman-maintainers PTAL |
yeah LGTM |
LGTM |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, timcoding1988 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
906f87b
into
containers:main
containers/automation_images#416
Does this PR introduce a user-facing change?