You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vmnet framework in macOS 15 can only provide networks where the attached containers are isolated from one another. Container-to-container communication over the virtual network is not possible.
Is it possible to block container-to-container communication on macOS 26 (without creating a new network for each of them)? I haven't found an option for it. While the containers don't see each other's traffic by default, using e.g. arpspoof they can.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The docs say:
Is it possible to block container-to-container communication on macOS 26 (without creating a new network for each of them)? I haven't found an option for it. While the containers don't see each other's traffic by default, using e.g. arpspoof they can.
Beta Was this translation helpful? Give feedback.
All reactions