Replies: 1 comment
-
For what it’s worth, I believe this may be the answer I am looking for. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I realize this is an extreme edge-case, and possibly not even a colima issue, however I have run into it nonetheless and am hoping someone has overcome the issue I'm running into.
My home network's DNS servers operate in 192.168.64.0/24, which also appears to be the subnet that colima chooses for a VM when specifying
--network-address
.As such, whenever I run colima with the
--network-address
feature enabled, I can no longer reach my DNS servers :(Is there any way of hinting to the VZ framework to use a different subnet other than 192.168.64.0/24?
Beta Was this translation helpful? Give feedback.
All reactions