-
-
Notifications
You must be signed in to change notification settings - Fork 653
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 start containers in macOS Mojave 10.14.1 #424
Comments
There seems to be an issue with Docker I would suggest to downgrade Docker back to |
@d4rkm1nd54 could you try out the release branch: #416 Please pay special attention to the instructions in the PR description. |
@d4rkm1nd54 any updates from your side? |
@d4rkm1nd54 see also here: #542 |
@d4rkm1nd54 from what I've seen, this is not related to MySQL, but to the custom paths you've applied in |
Stale issue This issue was marked with Beep beep, I am a bot - do not reply to me. |
Have just come back to Devilbox after a couple months of not using it, pulled the latest commits and found that I'm encountering this same issue. Seeing it on Windows 10 with Docker 18.09.2 and on Arch Linux with Docker 18.09.5-ce. @cytopia have you been able to confirm that reverting all HOST_PATH_*_DATADIR values to default fixes the issue? |
Can you confirm that this issue still persists after:
Also note that |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
ISSUE TYPE
Checklist
.env
file is attacheddocker-compose.override.yml
is attached (if it exists)cfg/
dir are attached (if customized)docker-compose logs
andlog/
output is added.env file:
OS / ENVIRONMENT
SUMMARY
With a fresh install of devilbox, can not start it with
docker-compose up httpd mysql php
I get the error:
Any other command with docker-compose fails with the same error (docker-compose down, stop, kill, rm...)
STEPS TO REPRODUCE
Fresh install following https://github.com/cytopia/devilbox#quick-start instructions and try to start containers with
docker-compose up
EXPECTED BEHAVIOUR
Containers start properly
ACTUAL BEHAVIOUR
The httpd container does not start
OTHER INFORMATION
Start command
File and user permissions (Linux & MacOS)
Empty folder
The text was updated successfully, but these errors were encountered: