I am unable to start docker desktop tool on mac Ventura 13.1, I keep getting fatal error
com.docker.supervisor cannot start Exit code 9
I tried already to uninstall and install docker again and also by manually removing docker files but nothing is working.
any help will be appreciated.
Related
I have recently upgraded the Mac OS to Ventura 13.2.1 and Xcode to 14.2, now once I try to compile any application with Xcode, I am getting Kill:9 related issue for random task/framework in the project. I also get Kill:9 issue sometime on terminal as well.
Listing the errors here:
failed to read asset tags: The command `` terminated with uncaught signal 9. The command had no output.
Driver threw jobFailedWithNonzeroExitCode(9, "") without emitting errors.
Unable to execute command: Killed 9 Clang frontend command failed due to signal.
Please help me to resolve this issue/crash.
Open project in Xcode.
Build the app with Simulator (I tried with iPhone 14 Pro)
Error occurs in the build
Ideally project should have compiled without any error.
It sounds to me that the problem is with the installation of Xcode because when an unprivileged task is attempted, the OS will kill it off (with signal 9).
What I recommend is for you to re-install Xcode.
When you first run the new Xcode, it should prompt you for an administrator password in order to install system related components. Make sure you do this step. Hopefully that should then allow you to compile and run your iOS apps.
I am using M1 MacBook and whenever I run docker-compose up, I am getting this error:
rosetta error: /var/db/oah/279281327407104_279281327407104/96e41f4a9e8ce9a3936f9793f20cc23d4cf4802260a5c9d638a6be89edb9f146/docker-compose.aot: attachment of code signature supplement failed: 1
whenever I run docker-compose up. The YAML file has basic boilerplate code that I copied from docker hub Wordpress. I wasn't getting this error 4 days ago though.
I'm getting a strange error popup I suspect it has something to do with a built in integration of Docker in IntelliJ.
I'm running the following:
Mac OS Big Sur 11.4
IntelliJ 21.1.3
Docker Desktop 3.5.2.18
Docker version 20.10.7, build f0df350
When I launch Docker Desktop, it launches IntelliJ for some reason and I get an error popup immediately:
Title: Cannot execute command
Body: Can not open file /Users/myuser/Library/Containers/com.docker.docker/Data/--list-extensions
I've tried reinstalling both several times and used the Clear cache and clear data options in the Docker settings. I should also note that i've tried removing all projects from IntelliJ and docker and have even disabled the "Docker" plugin in IntelliJ but still get the same error.
Does anyone have any ideas on how to prevent this popup on launch? It is more of an annoyance than a blocker as I can simply close it and then use the tools without problems but its odd that this would happen. Originally I dismissed it as some random system specific configuration but today found that it is not specific to my environment as I got it on a fresh install on a new machine with new user.
It seems a bug of Docker Development Environments Preview. The IntelliJ IDEA is opened by this process.
/Applications/Docker.app/Contents/MacOS/com.docker.dev-envs
You can degrade the Docker Desktop to version 3.4.0 to temporarily fix this problem.
What worked for me today:
Upgrade to Big Sur (wanted to do that anyway).
Remove Intelli-J
Uninstall Docker
Install Docker 3.6.x
Install latest Intelli-J
Problem gone.
dev. environment
OS: Mac OS
npm version: 4.6.1
I simply init the project with command expo init my-app and start the project.
Then, I select the Run on ios server and get the error message like in the above image.
Is there anyone who can fix this error?
Thank you for your help in advance.
I fixed this error with restarting my Mac
I have iOS project and have add CocoaPos. It was working fine with Mac OSX EL Capitan. Just upgraded my OS to macOS Sierra and the project stopped working.
When I building the project getting compile error in all CocoaPods target.
Command /bin/sh failed with exit code 133
I have Xcode 8.0.
I am not 100% sure this will help without further info but I had a similar issue. I had to run the following update then my issue was fixed:
sudo gem update gh_inspector
Hope it helps.