-
Notifications
You must be signed in to change notification settings - Fork 14
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
Comments
@YG1975 There was a very recent upgrade of Docker to v4.18. Do you have it? Could that be causing a conflict? |
Thank you @carlosrochoa . No I have Docker v4.17.0... so I guess this is not the cause unfortunately... |
I think that was a big upgrade, so maybe doing it might help with the problem? |
Thank you; I just upgraded Docker to 4.18 but no change unfortunately... |
Is that related to #413? ls -l /var/run/docker.sock |
You could try restarting the daemon if the local socket is not symlinked
|
ok, same issue as #413 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 |
Yes indeed such a message appeared... and I ignored it. I just tried the command (in sudo) and it worked beautifully! |
I'm not sure. You could try to set
or
in Described here : |
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
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:
The text was updated successfully, but these errors were encountered: