-
Notifications
You must be signed in to change notification settings - Fork 4
fix: mount vroom volume to the storage option default #653
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Docker bind mount to
/tmp/sentry-profilesfails because the host directory is not created, preventing vroom service startup.Severity: CRITICAL | Confidence: 1.00
🔍 Detailed Analysis
The configuration in
devservices/config.ymlchanges the vroom service to use a host path bind mount to/tmp/sentry-profilesinstead of a Docker named volume. When a developer attempts to run the vroom service via devservices, Docker will fail to start the container because the host directory/tmp/sentry-profilesdoes not exist. There is no logic in the Dockerfile, vroom code, or setup scripts to create this directory, nor is there documentation requiring developers to pre-create it.💡 Suggested Fix
Ensure the
/tmp/sentry-profileshost directory is created before the Docker container attempts to bind mount it. This can be achieved by adding amkdircommand to a setup script or the Dockerfile, or by reverting to a Docker named volume.🤖 Prompt for AI Agent
Did we get this right? 👍 / 👎 to inform future reviews.