Skip to content
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

Update base image to Alma Linux 9 #1

Merged
merged 8 commits into from
Jul 31, 2024
Merged

Update base image to Alma Linux 9 #1

merged 8 commits into from
Jul 31, 2024

Conversation

ebocchi
Copy link
Contributor

@ebocchi ebocchi commented Jun 10, 2024

No description provided.

@ebocchi ebocchi self-assigned this Jun 10, 2024
@rptaylor
Copy link
Contributor

@ebocchi thanks for starting this! I can deploy and test this but we need the image to be built first.
If merged I guess this will currently overwrite the image used in production gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid:4.17-2.1.

Do you think it would make sense to merge with BASE_TAG updated to 'gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid-el9' to make a separate EL9 image for testing purposes?

@rptaylor
Copy link
Contributor

rptaylor commented Jun 10, 2024

As a separate/independent next step I started sciencebox/charts#124 to prepare the chart for a squid update to v5.

@ebocchi
Copy link
Contributor Author

ebocchi commented Jun 17, 2024

@ebocchi thanks for starting this! I can deploy and test this but we need the image to be built first. If merged I guess this will currently overwrite the image used in production gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid:4.17-2.1.

Do you think it would make sense to merge with BASE_TAG updated to 'gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid-el9' to make a separate EL9 image for testing purposes?

Tagged as gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid:el9-4.17-2.1

@rptaylor
Copy link
Contributor

Thanks @ebocchi , I tried it on a dev cluster, and ran cvmfs_config chksetup and ALRB db-fnget tests on the squids.
I did not see any problems. I think it should be okay to use in production.

Do you think it makes sense to merge with the same 4.17-2.1 tag so that it will start to be used transparently? I'm okay with whatever would be easiest.

@rptaylor
Copy link
Contributor

@ebocchi any further thoughts on this? I think it's okay to merge, however you want to handle the tag version is fine with me.

@rptaylor
Copy link
Contributor

I built and pushed a new image to gitlab-registry.cern.ch/sciencebox/docker-images/frontier-squid:4.17-2.1.el9

@rptaylor
Copy link
Contributor

I deployed this image using chart frontier-squid-0.1.7 on our dev cluster, and run the ALRB db-fnget test and cvmfs_config chksetup on a node, all looked fine.

Squid pod logs and squidclient mgr:info also look fine.

@rptaylor
Copy link
Contributor

Summary of changes:

  • update to base image cern/alma9-base:20240701-2
  • update Dockerfile to use DNF
  • update version tag to have .el9 at the end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants