Upgrade CVMFS version in client container #262
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ocaisa
commented
Dec 4, 2025
| @@ -1,4 +1,4 @@ | |||
| ARG cvmfsversion=2.13.0 | |||
| ARG cvmfsversion=2.13.3 | |||
Member
Author
There was a problem hiding this comment.
@casparvl said that he actually used 2.13.3...so this may not actually fix anything (and just means I couldn't reproduce the problems he saw)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I used this version to play around with CVMFS shrinkwrap yesterday, and did not see the issues that @casparvl saw in cvmfs/cvmfs#3958 (RAM usage would rise and fall, never going above about 4GB)