-
Notifications
You must be signed in to change notification settings - Fork 321
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
centos URL used for RedHat8, Rocky8, and Alma8 #998
Comments
Hi, I assume the problem is that CentOS 8 is EoL, so they don't update it anymore. For Rocky/Alma, they should use the rhel dir, not centos. Are you able to provide a PR for this? |
Created pull request #999 and am testing this fix in our environment. |
confirmed the fix. We'll use my fork in our Puppetfile until the pull request is merged. |
Looks like pull request #999 is blocked by CLA. The latest version of docker in the centos folder is 26.1.3 and the 26.1.x family went End of Life on 17 February 2025. I've mentioned jbagleyjr in the hope that they can resolve the CLA check. Given it's a one liner and has become a higher priority I happy to create a new PR if the CLA issue can't be resolved soon. |
Sorry for the delay on my pull request. I had sent the CLA to my legal department and never heard back. I've signed it today for myself personally and not for the company I work for. |
Describe the Bug
Incorrect URL is used for the package_ce_source_location that includes "/centos/" which the docker stopped updating ~5 months ago.
Expected Behavior
Latest docker-ce package should be installed but were getting an older version because the incorrect repo URL is used.
Steps to Reproduce
Apply on any Rocky8, Alma8 or RedHat8. Docker version installed is 26 but should be 27.
Environment
Additional Context
Compare these two repos:
https://download.docker.com/linux/rhel/8/x86_64/stable/Packages/
https://download.docker.com/linux/centos/8/x86_64/stable/Packages/
Seems like the rhel repo would be appropriate for our rocky and alma servers.
The text was updated successfully, but these errors were encountered: