I installed the new version of Docker toolbox on a fresh machine. The install stated it was a success, yet when I start up the Docker Quickstart Terminal app, I get an odd error.
AppleEvent timed out.
Terminal got an error: AppleEvent timed out. (-1712)
Googling this error proved to be fruitless.
I uninstalled and reinstalled
I restarted
I uninstalled, restarted, changed networks, and so on.
Has anyone else had these errors?
OSX YOSEMITE
Related
I'm on MacOS 12.1. I downloaded Docker Desktop from the Docker site, but when starting it, I always get the following error:
level=error msg="Handler for GET /v1.24/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again."
How can I resolve this problem? All the results I can find for this error already have the daemon started and working. I can't even get the daemon started. I haven't ever touched docker swarm.
Running any of the suggested commands fails because there is no running docker daemon.
Reseting to factory defaults does not resolve the issue.
Reinstalling Docker Desktop does not resolve the issue.
Reinstalling the Docker cli does not resolve the issue.
Restarting the machine does not resolve the issue.
What do I do to fix this issue?
What I ended up doing was uninstalling Homebrew. Apparently something there was causing issues, even though I didn't install Docker Desktop through brew, and made sure to uninstall all formulas that had anything to do with Docker. Exactly what caused this problem is a mystery still.
I had the same problem.
And I found this log is catched from ~/Library/Containers/com.docker.docker/Data/log/vm/dockerd.log
I try to restart Docker Desktop, but this log doesn't append any content. The strange thing is error Dialog display the same content, even time! Which means Docker Desktop never try to start docker daemon.
I try to close Wi-Fi, then Docker Desktop will start normally.
Check dockerd.log again, this print the same error with new time, but Docker Desktop running normally.
So I think there is some error relate Docker Desktop network process rather than docker daemon.
Additionally, maybe docker daemon printed this error because of network driver is overlay which require a swarm node.
After getting numerous messages saying I should upgrade my OS, I have finally decided to upgrade to macOS Big Sur v11.6.1.
Unfortunately, docker doesn't work anymore.
I'm getting an error:
Fatal Error
Docker daemon failed to start
and
2021-12-07T09:47:14Z dockerd time="2021-12-07T09:47:14.957430297Z" level=debug msg="Calling GET /version"
I can see the option to Reset Docker to factory defaults but I'm afraid of resetting because it means I will also erase all my docker images.
Is there any easy way to fix this issue without erasing my work?
I get this fairly often on my Mac. I'm still on Big Sur.
This in the terminal seems to get me working (pay attention to the capitalisation):
pkill Docker
open -a /Applications/Docker.app
The com.canonical.multipassd service is constantly logging errors on my Mac and multipass won't work at all, even after reinstalling, rebooting, and updating my Mac.
In an attempt to use my GPU in a Linux VM through multipass, I tried to install the AMDGPU driver for my card (Radeon Pro 5300 4GB). I had installed multipass through brew and made some progress, but the ./amdgpu-install process was returning various errors as a result of missing dependencies. Having started to resolve the missing dependencies, in an attempt to build the driver again, the build just stopped halfway through and I couldn't terminate the process or get the VM to respond at all (didn't take a screenshot sorry).
Because of this, I closed the VM shell and tried to get multipass to shut down the VM. Multipass stopped responding altogether - the application just spun, and it didn't respond at all in terminal. I force quit multipass in Activity Monitor. That still didn't fix it, so I (somewhat stupidly) force quit 'hyperkit' and 'multipassd'. This is where everything went really wrong.
Having force quit 'multipassd', I tried to re-open multipass, but it returned the error below
list failed: cannot connect to the multipass socket
Please ensure multipassd is running and '/var/run/multipass_socket' is accessible
I looked this up and tried a few suggested solutions. I uninstalled multipass with Brew. I deleted the application, and reinstalled with brew. I also tried brew remove multipass, and tried installing using the .pkg from the multipass website. When that didn't fix it, I restarted my computer and reset NVRAM on startup. That also didn't make a difference, so I have just updated my Mac to MacOS 11.4, and it is still not fixed.
The console logs suggest that multipassd is still doing something, as it is continually logging in the system.log:
May 26 09:39:15 <myName> com.apple.xpc.launchd[1] (com.canonical.multipassd[2131]): Service exited with abnormal code: 1
May 26 09:39:15 <myName> com.apple.xpc.launchd[1] (com.canonical.multipassd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
In the multipass log, this message is also being generated about once every 10 seconds:
[error] [daemon] Caught an unhandled exception: Invalid MAC address
[warning] [Qt] QMutex: destroying locked mutex
These messages are being generated even after resetting NVRAM and rebooting. I think they're the cause of my issue launching multipass, but I haven't found any solution to stop them, and I can't identify any process that is still running related to multipass. As far as brew is concerned, multipass is not installed, but it's logs are still filling up...
Happy to provide console or terminal output if needed - nothing else on my Mac seems to be broken, I just can't use multipass now. I do have a time machine backup, so if that is guaranteed to fix it, I might just resort to the backup, but I'm not sure that would necessarily fix it, and I would rather find an alternative solution.
As this has probably made clear, I'm very new to Linux and VMs... any solutions greatly appreciated!
Fixed it!! I hadn't properly uninstalled it - the 'proper' uninstall script can be run using
sudo sh "/Library/Application Support/com.canonical.multipass/uninstall.sh"
Reinstalling multipass after running this command worked fine.
I foolishly upgraded my mac to mojave and once I did my elasticsearch (that I installed through Homebrew) stopped working. Since then I have reinstalled it several times and I continue to receive this error:
Exception in thread "main"
org.elasticsearch.bootstrap.BootstrapException:
java.nio.file.FileSystemLoopException:
/usr/local/etc/elasticsearch/elasticsearch
Likely root cause: java.nio.file.FileSystemLoopException:
/usr/local/etc/elasticsearch/elasticsearch
When I try and start it using brew services I get:
/Users/***/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist:
service already loaded
Error: Failure while executing; '/bin/launchctl bootstrap gui/501
/Users/****/Library/LaunchAgents/homebrew.mxcl.elasticsearch.plist'
exited with 133.
The only way I can get elasticsearch to start currently is running it through docker
Has anyone else seen this issue?
I see a couple of entires for this error but not on Windows 7. I have installed Client version 1.5.0 (Client API 1.17) in to my Windows 7 SP1 machine. I followed the Windows Install instructions with no problem. I run Boot2Docker Start and it is started successfully. However, when I run the docker version command I am informed on version details with a FATA error message below stating:
FATA[0000] Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
When I run docker -d I am told there is a permission error:
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
FATA[0000] open /var/run/docker.pid: permission denied
I have tried a chmod on the pid file and have checked I am running with Administrator privilege on the Windows machine. I am not sure whether the permission denied is a red herring.
As it appears Windows 7.1 is supported and the install appeared to run smoothly without errors, I am wondering if anyone has come across this problem or has any ideas as to what try next?
Many thanks, rvon