Skip to content

Conversation

@AkihiroSuda
Copy link
Member

@AkihiroSuda AkihiroSuda commented Jun 6, 2024

Add back EL 8 to test legacy compatibility

Follow-up to:

matrix:
box:
- fedora/39-cloud-base
# the upstream rockylnux/8 image no longer works:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're keping Rocky Linux 8 to test compatibility, can you add a comment to the file so it doesn't get changed again?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just remove the rockylinux/9 one as well?

I notice in Vagrant Cloud images can be hosted externally, but then the link dies after a year or two and the image is unusable. This is also happening with the fedora 37 images. If we use one should we just use all the bento images since they are hosted by vagrant cloud?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rockylinux/9

Probably safe to retain

Vagrant Cloud

Maybe we can just switch away from Vagrant to Lima
Mirantis/cri-dockerd@a3a2995

Copy link
Member

@akhilerm akhilerm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this for checking the compatibility of older glibc as mentioned here, or is it something else that we are validating?

@AkihiroSuda
Copy link
Member Author

Is this for checking the compatibility of older glibc as mentioned here, or is it something else that we are validating?

glibc, cgroup v1, kernel, SELinux policies, and whatever

- fedora/39-cloud-base
# the upstream rockylnux/8 image no longer works:
# https://github.com/containerd/containerd/pull/10297
- bento/rockylinux-8
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still failing
https://github.com/containerd/containerd/actions/runs/9395253328/job/25885528463?pr=10304

==> default: Starting domain.
==> default: Domain launching with graphics connection settings...
==> default:  -- Graphics Port:      5900
==> default:  -- Graphics IP:        127.0.0.1
==> default:  -- Graphics Password:  Not defined
==> default:  -- Graphics Websocket: 5700
==> default: Waiting for domain to get an IP address...
==> default: Removing domain...
==> default: Deleting the machine folder
/root/.vagrant.d/gems/3.1.4/gems/fog-core-2.4.0/lib/fog/core/wait_for.rb:9:in `block in wait_for': The specified wait_for timeout (2 seconds) was exceeded (Fog::Errors::TimeoutError)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to Alma Linux 8

Add back EL 8 to test legacy compatibility

Follow-up to PR 10297

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@AkihiroSuda AkihiroSuda force-pushed the ci-add-back-rocky8 branch from 5cc53a7 to 08c1e12 Compare June 8, 2024 10:50
@AkihiroSuda AkihiroSuda changed the title CI: add back Rocky Linux 8 CI: add back EL 8 Jun 8, 2024
@AkihiroSuda AkihiroSuda marked this pull request as ready for review June 8, 2024 11:17
@samuelkarp samuelkarp added this pull request to the merge queue Jun 10, 2024
Merged via the queue into containerd:main with commit 4a18adc Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants