Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker desktop start stop loop on m1 #6136

Closed
3 tasks done
h4l-yup opened this issue Jan 16, 2022 · 4 comments
Closed
3 tasks done

docker desktop start stop loop on m1 #6136

h4l-yup opened this issue Jan 16, 2022 · 4 comments

Comments

@h4l-yup
Copy link

h4l-yup commented Jan 16, 2022

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID:829BCAB8-5664-4B50-9920-95B5EF3B645E/20220116131508

Expected behavior

It should be started.

Actual behavior

2022-01-16.10.25.07.mov

I have read #5477, #5483 and tried the solutions that are mentioned but none of them worked for me.
The docker desktop looping between start status and stop status and I can not access to preferences.
Resetting on debug tab does not work either.
This just happened when I changed some settings on preference page and I updated the app (maybe to 4.4.2 and I don't know the previous version that was installed but I installed the app two days ago from website so it would be the right before released version)
Also, I am not using internet sharing so it is not the reason.

Information

  • macOS Version: 12.0.1
  • Intel chip or Apple chip: Apple Chip (M1 Pro)
  • Docker Desktop Version: 4.4.2 (73305)

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

Steps to reproduce the behavior

  1. ...
  2. ...
@danbka33
Copy link

danbka33 commented Jan 17, 2022

Same. Started after change cpu and memory settings on preference

Diagnostics ID. D7AEF805-8C6F-466C-925E-D0C500E5710D/20220117105218

@fredericdalleau
Copy link

Hi @h4l-yup and @danbka33,
For both of you, the diagnostics reports an error because too many cpus are configured.
As a workaround, could you try lowering the number of requested processors in the settings file ?
The settings file is located at ~/Library/Group\ Containers/group.com.docker/settings.json
You would need to replace the line "cpus": 10 with "cpus": 8 as this is the maximum value we currently support.
We are working on a fix.
Thanks,
Frédéric Dalleau

@danbka33
Copy link

Hi @h4l-yup and @danbka33, For both of you, the diagnostics reports an error because too many cpus are configured. As a workaround, could you try lowering the number of requested processors in the settings file ? The settings file is located at ~/Library/Group\ Containers/group.com.docker/settings.json You would need to replace the line "cpus": 10 with "cpus": 8 as this is the maximum value we currently support. We are working on a fix. Thanks, Frédéric Dalleau

Thanks, this solved the problem.

#6063

@h4l-yup h4l-yup closed this as completed Jan 18, 2022
@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Feb 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants