`vmnet.sock: connect: permission` when using `--network-address`
- 主要語言
- Go
- 星號
- 30.8k
- 分支
- 613
- PR 合併指標
- 30 天內沒有已合併 PR
描述
### Description
Even when using `--network-address` the VM doesn't get assigned an IP address, making the containers not accessible from outside.
### Version
Colima Version: 0.6.0
Lima Version: 0.18.0
Qemu Version: 8.1.2
### Operating System
- [ ] macOS Intel <= 12 (Monterrey)
- [ ] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [X] macOS M1 >= 13 (Ventura)
- [ ] Linux
### Output of `colima status`
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/mfincato/.colima/default/docker.sock
### Reproduction Steps
1. `colima start --network-address`
2. No address is being assigned to Colima
### Expected behaviour
Colima should assign an IP address to the VM, to allow external access. Instead the log shows:
```bash
INFO[0000] starting colima
INFO[0000] runtime: docker
INFO[0001] preparing network ... context=vm
WARN[0017] error starting vmnet: error at 'preparing network': vmnet socket file error: dial unix /Users/mfincato/.colima/default/daemon/vmnet.sock: connect: permission denied context=vm
INFO[0017] creating and starting ... context=vm
INFO[0045] provisioning ... context=docker
INFO[0045] starting ... context=docker
INFO[0046] done
```
### Additional context
I've already completely tried uninstalling, deleting all files, and reinstalling Colima and all its dependencies.
貢獻指南
這個儲存庫沒有索引到貢獻指南
評估
這個 Issue 還沒有評估資料。