Cache bust bundle data to fix docker builds #679
Merged
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
Jamie had an issue running and building the new docker file that might affect other people. I can't reproduce this myself and I didn't have this problem when upgrading ruby so I wonder if it's caused by earlier versions of bundler or binstubs in the shared folder. Modern versions of bundler will install the bundler version specified in the gemfile automatically, 2.x was the version version to do this so maybe there were some teething issues that are now fixed. ``` api-1 | Activating bundler (~> 4.0) failed: api-1 | Could not find 'bundler' (~> 4.0) - did find: [bundler-2.7.2,bundler-2.6.9] api-1 | Checked in 'GEM_PATH=/root/.local/share/gem/ruby/3.4.0:/usr/local/lib/ruby/gems/3.4.0:/usr/local/bundle' , execute `gem env` for more information api-1 | api-1 | To install the version of bundler this project requires, run `gem install bundler -v '~> 4.0'` ```
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request addresses Docker build issues that occurred after the Ruby and Bundler upgrade in PR #668. The issue manifested as bundler version conflicts where the container couldn't find the required bundler version (~> 4.0) because an older version was cached in the shared Docker volume.
Changes:
- Renamed the Docker volume from
bundle-datatobundle-data-v2to invalidate stale bundler cache from the previous Ruby environment
mwtrew
approved these changes
Feb 12, 2026
Contributor
mwtrew
left a comment
mwtrew
left a comment
There was a problem hiding this comment.
Can't reproduce it myself, but I agree that was probably the issue and that this should fix it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Jamie had an issue running and building the new docker file that might affect other people likely caused by #668
I can't reproduce this myself and I didn't have this problem when upgrading ruby so I wonder if it's caused by earlier versions of bundler or binstubs in the shared folder. The base docker image was changed so the only state that I think could be affecting it is in the shared bundler volume set up by docker compose.
Modern versions of bundler will install the bundler version specified in the gemfile automatically, 2.x was the version version to do this so maybe there were some teething issues that are now fixed.
Original error: