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
networks.Validate() requires that socket_vmnet is owned by root
This restriction was weakened by #1220
to only require the file and directories to be owned by the admin user, but
that configuration is not secure.
If users are willing to run an insecure configuration, then they can always
enable password-less sudo, which does not need a sudoers file at all.
Signed-off-by: Jan Dubois <[email protected]>
Copy file name to clipboardExpand all lines: website/content/en/docs/config/network/_index.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,10 +69,17 @@ The configuration steps are different for each network type:
69
69
#### Managed (192.168.105.0/24)
70
70
71
71
[`socket_vmnet`](https://github.com/lima-vm/socket_vmnet) is required for adding another guest IP that is accessible from the host and other guests.
72
+
It must be installed according to the instruction provided on https://github.com/lima-vm/socket_vmnet.
73
+
74
+
Note that installation using Homebrew is not secure and not recommended by the Lima project.
75
+
Homebrew installation will only work with Lima if password-less `sudo` is enabled for the current user.
76
+
The `limactl sudoers` command requires that `socket_vmnet` is installed into a secure path only
77
+
writable by `root` and will reject `socket_vmnet` installed by Homebrew into a user-writable location.
72
78
73
79
```bash
74
-
# Install socket_vmnet
75
-
brew install socket_vmnet
80
+
# Install socket_vmnet via MacPorts or from source
81
+
# using instructions on https://github.com/lima-vm/socket_vmnet
82
+
…
76
83
77
84
# Set up the sudoers file for launching socket_vmnet from Lima
0 commit comments