macOS: cannot add network services: adding watcher failed #3145
Comments
|
This appears to only happen with |
|
The file Is the file a symlink? If yes, does it point to an existing socket file? I assume if you delete or rename the file, Lima will work normally. You could also try to reboot your machine; it will clear out old stuff from I think this issue is related to containers/gvisor-tap-vsock#462 |
$ ls -al /private/var/run/mdnsd_aud
lrwxr-xr-x 1 root daemon 22 Jan 24 16:10 /private/var/run/mdnsd_aud -> /var/run/mDNSResponderI presume you found this thread - looking through that gave me a hint as to where the problem arose. ggrep -irl mdnsd_aud /Library/Application\ Support/Audinate
/Library/Application Support/Audinate/ConMon.bundle/Contents/MacOS/launch_conmon.shcat /Library/Application\ Support/Audinate/ConMon.bundle/Contents/MacOS/launch_conmon.shYields: #!/bin/sh
# Redirect legacy responder to current
MDNSD_PIPE=/var/run/mdnsd_aud
rm -f "${MDNSD_PIPE}"
ln -s /var/run/mDNSResponder "${MDNSD_PIPE}"
exec "/Library/Application Support/Audinate/ConMon.bundle/Contents/MacOS/conmon_cmm" "$@"This looks like something Audinate puts in place to make either Dante Controller or Dante Virtual Soundcard work correctly. As you correctly suggested, deleting that file causes lima to work just fine. Presumably there aren't a ton of individuals using both Dante Virtual Soundcard and/or Dante Controller and also trying to leverage All of that said, it seems like having that symlink there shouldn't cause lima to not work, correct? |
Yes, but it is an issue with |
|
It is very ironic that I experienced this in addition to the issue w/ Thanks for the help! Closing. |
|
I'm seeing this on DDEV test runners (pre-existing instance) since the v1.0.4 release /var/run/docker.sock is a symlink (to Orbstack). This never prevented lima from starting before. And it has its own socket... |
|
@rfay It is a new issue introduced in gvisor-tap-vsock 0.8.2 via containers/gvisor-tap-vsock#450. |
|
Hi, same issue with Lima 1.0.4: I use Docker Desktop and it creates the socket. |
|
@jandubois I think this might be a logic error in lima, because it's trying to use a socket that it doesn't own. It's trying to use /var/run/docker.sock, but it's got a different docker context that it should be using, so is it accidentally using /var/run/docker.sock? I'm trying to add a workaround for DDEV tests, but I don't think lima should fail to run just because an unrelated docker provider is running using an unrelated docker.sock. |
|
Just a note that this breaks Colima in the same way, as one would expect. I don't imagine there are too many folks out there running multiple docker providers, but at least a couple of us have already showed up. |
@rfay The error is in |
|
Hey folks! Adding few my bits here! Fix that worked for me:
then |
This is the one command that fixed the entire issue for me. |
|
FYI: all the recent refactoring of DNS code in So all the file watching code should be gone in the next release. |
|
@rfay gvisor-tap-vsock has just been updated to 0.8.3, which reverts all the DNS related changes since 0.7.5. It would be great if you could verify that your issues are resolved with the latest Lima |
|
I'm happy to check! A casual review of docs didn't turn up any build instructions, and simple I guess it requires CGO_ENABLED=1 and clang refuses to do that on my mac m1 ? I did get an apparent successful build with (that did get After a bit more fiddling I got a failure to |
|
Oh, forgot about I confirm that So all is good, thanks! (Build instructions would be a great addition to the README. Maybe they're there and I just didn't find them...) |
Thank you for confirming.
They are slightly hidden: There is a link to the docs for "more information", and the Installation page contains a tab to show how you build from source. However, it is pretty straight forward: |
Oops, I see that you tried that, and it didn't work. Which is weird, because I've been running it thousands of times (well, I normally run |
|
@rfay If you want to debug this, then I would run |
|
Here's the result: `make clean and make --dry-run`And... |
|
@rfay There must be something wrong with your rfay@MacBookAir:~/workspace/lima$ make clean
clang: error: no such file or directory: 'go'
clang: error: no such file or directory: 'env'
clang: error: no such file or directory: 'GOVERSION'
clang: error: no input files
rm -rf _output vendorThe |
|
The The only thing I can come up with is that you have a ❯ GO="clang go" make clean
clang: error: no such file or directory: 'go'
clang: error: no such file or directory: 'env'
clang: error: no such file or directory: 'GOHOSTARCH'
clang: error: no input files
...Anyways, I'll stop now; I'm sure the root cause is in your build setup and not the Lima repo. |
|
Several Since I don't know where those came from. There may be something wrong with the use of $(CC) in the awk stuff in the Makefile but I don't think it's worth studying. |
I agree that it is probably not worth it, but maybe you could still test if simply adding quotes would fix it? - ENVS__output/bin/limactl$(exe) = CGO_ENABLED=1 GOOS=$(GOOS) GOARCH=$(GOARCH) CC=$(CC)
+ ENVS__output/bin/limactl$(exe) = CGO_ENABLED=1 GOOS=$(GOOS) GOARCH=$(GOARCH) CC="$(CC)" |
Description
Hi, I am brand new to using
lima, and for some reason I cannot seem to start any VM's. When I trylimactl start --log-level=trace, I get the following:The error log shows the following:
That last line seems to be the problem:
{ "level": "fatal", "msg": "cannot add network services: adding watcher failed: \"/private/var/run/mdnsd_aud\": operation not supported on socket", "time": "2025-01-23T17:21:15-05:00" }I can't seem to find any other issues related to this, nor anything in GitHub discussions. I am not sure how to proceed with troubleshooting. I have tried different templates, deleted the
${HOME}/.limaand${HOME}/Library/Caches/limadirectories to force re-download of the base image, all yield the same results.Lima Version
macOS Version
The text was updated successfully, but these errors were encountered: