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

Can not restart AccessMod Docker version after re-starting my computer #416

Open
YG1975 opened this issue Apr 21, 2023 · 11 comments
Open

Can not restart AccessMod Docker version after re-starting my computer #416

YG1975 opened this issue Apr 21, 2023 · 11 comments

Comments

@YG1975
Copy link

YG1975 commented Apr 21, 2023

Current Behavior

AccessMod 5.8.1.alpha.1 Docker version was working fine until yesterday. Today I had to restart my computer and AM does not launch anymore

image

image

Expected Behavior

Possible Solution

Steps to Reproduce

After starting Docker, not possible to launch AccessMod

Detailed Description

Docker seems to run fine and resources allocated sufficient:
image
image

@carlosrochoa
Copy link
Collaborator

@YG1975 There was a very recent upgrade of Docker to v4.18. Do you have it? Could that be causing a conflict?

@YG1975
Copy link
Author

YG1975 commented Apr 21, 2023

Thank you @carlosrochoa . No I have Docker v4.17.0... so I guess this is not the cause unfortunately...

@carlosrochoa
Copy link
Collaborator

I think that was a big upgrade, so maybe doing it might help with the problem?

@YG1975
Copy link
Author

YG1975 commented Apr 21, 2023

Thank you; I just upgraded Docker to 4.18 but no change unfortunately...

@fxi
Copy link
Collaborator

fxi commented Apr 21, 2023

Is that related to #413?
What's the output of

 ls -l /var/run/docker.sock

@fxi
Copy link
Collaborator

fxi commented Apr 21, 2023

You could try restarting the daemon if the local socket is not symlinked

sudo launchctl kickstart system/com.docker.socket

@YG1975
Copy link
Author

YG1975 commented Apr 21, 2023

Here is the output of ls -l /var/run/docker.sock:
image

@YG1975
Copy link
Author

YG1975 commented Apr 21, 2023

The daemon restart does not seem successful either:
image

@fxi
Copy link
Collaborator

fxi commented Apr 21, 2023

ok, same issue as #413
You did not have something like this ? Docker should make sure this link exists. If not, it could be a bug on their side. Or something on your system...
W1euE

However... the fix is to launch this command after each restart as /var/run is mounted as a temporary file system. Docker should do this itself via launchd, but it's possible you opt-out this option by mistake.

ln -s -f ~/.docker/run/docker.sock /var/run/docker.sock 

@YG1975
Copy link
Author

YG1975 commented Apr 21, 2023

Yes indeed such a message appeared... and I ignored it. I just tried the command (in sudo) and it worked beautifully!
Thank you so much!
Is there anything I can do to fix it permanently in Docker?

@fxi
Copy link
Collaborator

fxi commented Apr 21, 2023

I'm not sure. You could try to set

 "authDeclinedInstallSettings": true,

or

 "authDeclinedInstallSettings": false,

in ~/Library/Group\ Containers/group.com.docker/settings.json
(using a text editor, not a word processor)

Described here :
docker/for-mac#6634 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants