-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Add socket mount support with --mount flag #33
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
11 commits
Select commit
Hold shift + click to select a range
ab26866
feat: add socket mount support with --mount flag
rubionic f4b77cd
test: update tests to use mount-N naming and add format scripts
rubionic ac4a1f6
fix: address PR review feedback
rubionic 9bfcd5b
fix: add period to Mount struct comment to trigger CI rebuild
rubionic b83414c
fix: clear Go cache in CI to resolve corrupted cache issue
rubionic 5554632
fix: skip golangci-lint cache to resolve corrupted cache issue
rubionic 31bb526
fix: rename duplicate Mount type to ClusterMount
rkoster 52c7421
fix: address PR code review feedback
rubionic db1cb62
feat: add Mounts field display to list command
rubionic 86fa7a6
fix: add Docker socket mount support to Kind cluster
rubionic 0fb3dac
fix: revert devbox files from symlinks back to regular files
rubionic 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
Some comments aren't visible on the classic Files Changed page.
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
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
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.
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.
The mount path parsing uses strings.Split with ":" as the delimiter, which could cause issues if file paths contain colons. While colons are rare in Unix paths, they are valid characters. For example, a path like "/tmp/my:weird:path" would be incorrectly split into 4 parts.
Windows paths with drive letters (e.g., "C:/path") would also be problematic, though this seems to be a Linux/Unix-focused tool.
Consider documenting this limitation or using a more robust parsing approach that handles escaped colons or uses a different delimiter for the type field (e.g., "@" or using flags like
--mount-source,--mount-target,--mount-type).