lima-vm / lima-vm/lima

Can't create a socket in a shared directory

Open
#1,824 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

### Description

I am not sure if this is a limitation on the macOS side or something with qemu but when I try to create a socket in the vm it fails to even create the socket. I will continue to look into this issue but I wasn't sure if anyone else ran into this issue before.

```sh
'c. jemershaw@epona-work
,xNMM. --------------------
.OMMMMo OS: macOS 13.5.2 22G91 arm64
OMMM0, Host: Mac14,9
.;loddo:' loolloddol;. Kernel: 22.6.0
cKMMMMMMMMMMNWMMMMMMMMMM0: Uptime: 4 days, 17 hours, 28 mins
.KMMMMMMMMMMMMMMMMMMMMMMMWd. Packages: 103 (brew)
XMMMMMMMMMMMMMMMMMMMMMMMX. Shell: zsh 5.9
;MMMMMMMMMMMMMMMMMMMMMMMM: Resolution: 3840x1620
:MMMMMMMMMMMMMMMMMMMMMMMM: DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX. WM: yabai
kMMMMMMMMMMMMMMMMMMMMMMMMWd. Terminal: tmux
.XMMMMMMMMMMMMMMMMMMMMMMMMMMk CPU: Apple M2 Pro
.XMMMMMMMMMMMMMMMMMMMMMMMMK. GPU: Apple M2 Pro
kMMMMMMMMMMMMMMMMMMMMMMd Memory: 3053MiB / 16384MiB
;KMMMMMMMWXXWMMMMMMMk.
.cooc,. .,coo:.
```

To reproduce the issue:
```sh
# Start the ubuntu-lts vm
┗╸❯❯❯ limactl start template://ubuntu-lts
# list the ubuntu-lts vm
┗╸❯❯❯ limactl list ubuntu-lts
NAME STATUS SSH VMTYPE ARCH CPUS MEMORY DISK DIR
ubuntu-lts Running 127.0.0.1:55327 qemu aarch64 4 4GiB 100GiB ~/.lima/ubuntu-lts
# Login to the vm
┗╸❯❯❯ eval $(limactl show-ssh ubuntu-lts) -A
# Test that you can create a socket in the vm
jemershaw@lima-ubuntu-lts:~$ nc -lkUv aSocket.sock
Bound on aSocket.sock
Listening on aSocket.sock
^C
# navigate to a shared directory
jemershaw@lima-ubuntu-lts:~$ cd /Users/jemershaw
# Try to start a socket in the shared directory (fails)
jemershaw@lima-ubuntu-lts:/Users/jemershaw$ nc -lkU aSocket.sock
nc: Operation not supported
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.