Closed DuMaM closed 10 months ago
Ok, issue fixed by adding a user to staff
group which is the default for socket_vemn
sudo dseditgroup -o edit -a $USER -t user staff
socket_vmnet --hlep
socket_vmnet: unrecognized option `--hlep'
Usage: socket_vmnet [OPTION]... SOCKET
vmnet.framework support for rootless QEMU.
socket_vmnet does not require QEMU to run as the root user, but socket_vmnet itself has to run as the root, in most cases.
--socket-group=GROUP socket group name (default: "staff")
--vmnet-mode=(host|shared|bridged) vmnet mode (default: "shared")
--vmnet-interface=INTERFACE interface used for --vmnet=bridged, e.g., "en0"
--vmnet-gateway=IP gateway used for --vmnet=(host|shared), e.g., "192.168.105.1" (default: decided by macOS)
the next IP (e.g., "192.168.105.2") is used as the first DHCP address
--vmnet-dhcp-end=IP end of the DHCP range (default: XXX.XXX.XXX.254)
requires --vmnet-gateway to be specified
--vmnet-mask=MASK subnet mask (default: "255.255.255.0")
requires --vmnet-gateway to be specified
--vmnet-interface-id=UUID vmnet interface ID (default: random)
--vmnet-nat66-prefix=PREFIX:: The IPv6 prefix to use with shared mode.
The prefix must be a ULA i.e. start with fd00::/8.
(default: random)
-p, --pidfile=PIDFILE save pid to PIDFILE
-h, --help display this help and exit
-v, --version display version information and exit
version: 1.1.3
So was this an issue related to your socket_vmnet install? Or did the minikube update change anything? I can provide a link to minikube v1.31.2 if you are interested in doing any testing. From memory we haven't touched any QEMU code since v1.31.2 so it seems unlikely, but still possible.
It looks like it was due to a system upgrade which was aligned with minikube update via brew.
I've tried @DuMaM's suggested fix using v1.32.0, and it fails:
$ minikube start --driver qemu --network socket_vmnet
😄 minikube v1.32.0 on Darwin 14.3 (arm64)
✨ Using the qemu2 driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing qemu2 VM for "minikube" ...
OUTPUT:
ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused
🤦 StartHost failed, but will try again: driver start: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
🔄 Restarting existing qemu2 VM for "minikube" ...
OUTPUT:
ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused
😿 Failed to start qemu2 VM. Running "minikube delete" may fix it: driver start: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1
╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯
This issue still persists in recent versions ! Why is it closed ?
What Happened?
Error
Since upgrade to 1.32.0 I'm unable to connect to socket_vmnnet. ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Permission denied
Env Setup
Mac M1
minikube
qemu
socet_vmn
Attach the log file
Logs
Operating System
macOS (Default)
Driver
QEMU