-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
[BUG] Faulty startup on MacOS #115
Comments
If your dockerfile only has a from line in it, why not just use our image? Also read our documentation again as those ID Env's are wrong. |
I am manually pulling your image. Replaced the previous Dockerfile with a oneliner. DB_HOST is set but is not used, the rest should be fine according to your documentation, or am I missing something? The LLTUID/LLTGID are not used in the Dockerfile. |
Are you trying to use a pre-existing mariadb config? Also the NFS share is likely to cause issues as databases don't like remote mounts. |
I use the image as is, only adding some GRANTS to it and creating an empty db. This is, what i thought, there could be some issues with permissions thus quitting/hanging on startup. It's hard to tell, as the MacOS documentation on NFS is absolutely not sufficient and changelogs are not fully released for such components. Seems, some NFS problems arose. As stated in the other issue, NFS mounts are not supported by you, so i guess, this issue can be closed, as it works like a charm on Linux. Many thanks! |
docker/for-mac#6544 The fix can be found here for users of NFS |
Is there an existing issue for this?
Current Behavior
mysqld does not start, when accessing the container and trying to execute mysqld commands (-uroot)
ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
occurs. This problem however, does not exist on Linux (var. distros and prev. MacOS versions).
Expected Behavior
Startup of the mysqld service
Steps To Reproduce
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: