cctl: Make networking macOS 26 only #437
Open
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
There's no sane way to do networking in this tool on < 26, you have to guess the bridge subnet.
jglogan
reviewed
Dec 6, 2025
Contributor
jglogan
left a comment
jglogan
left a comment
There was a problem hiding this comment.
Just because it's not 100% sane doesn't mean you can't do it, right (we have the same problem in container)?
vmnet will tend to pick 192.168.64.1/24 as long as you aren't running anything else using a NAT bridge already.
Using ip and gateway on Tahoe is a bit dodgy since we're letting vmnet auto-select the network in that case. For that we really should have a ContainerManager.VmnetNetwork(subnet: String)
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.
There's no sane way to do networking in this tool on < 26, you have to guess the bridge subnet.