Replies: 3 comments 3 replies
-
I don't understand the question. How does it "not work"? Even if you do forward the port, it should still be usable inside the VM unless something else is listening on the port. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I think there is a typo there, in
|
Beta Was this translation helpful? Give feedback.
1 reply
-
can this be marked as answered? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi community! I would like to disable 2049 port forwarding so that in the guest VM I can do development that uses 2049 port by default. Is there a way to do so?
I tried to ignore 2049 forwarding by doing the following in default/lima.yaml:
But with this configuration, during boot, port 2049 is still forwarded.
My host machine is MacBook M3 Pro, macOS Sonoma 14.3. My guest VM is aarch64 Ubuntu.
vmType: vz
. I mounted one writeable directory in addition to the default read-only home directory. The mount type is virtiofs (as default for vz). forwardX11 enabled. Rosetta enabled.sudo ss -lptn 'sport = :2049'
reports that 2049 is actively listened, but the process name is empty:Thanks!
Beta Was this translation helpful? Give feedback.
All reactions