-
Notifications
You must be signed in to change notification settings - Fork 26
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] Mage docker container doesn't start with bind mounts on Windows #454
Comments
Hi @arminus, thank you for reporting this issue. We are aware that the bind mounts are not working as expected. We've recently had a similar discussion on another issue related to this and there were a few possible solutions mentioned, such as changing the file ownership and permissions, changing the default location of a docker data directory with the |
Sorry, didn't find memgraph/memgraph#1734 - I can confirm that the compose file given in memgraph/memgraph#1734 (comment) works for me in a sense that the volumes are created where I want them, but they are still not bind mounts (which is kind of our policy for docker data) Since so far, I'm testing Memgraph on Windows only, file ownership and permissions shouldn't normally be the cause. I'm using docker for a variety of purposes and bind mounts haven't been an issue for any so far, in particular not with Neo4J where I'm coming from in this case. (experience is different on Linux of course). |
We intend to work on improving the overall user experience with docker-compose soon so any feedback is valuable. I'll keep you updated on the topic. Is this currently a blocker for you? |
No, this is not a blocker - just "unusual" behavior |
This is + 1 in community: https://discord.com/channels/842007348272169002/1270687906087964702/1275360784167211048 |
Describe the bug
then it just exits with status 139 according to docker desktop.
To Reproduce
Steps to reproduce the behavior:
Run this compose on Windows 10 with docker desktop 4.26.1, directories ./mg_lib, ./mg_log and ./mg_etc have been created before running docker compose up
Expected behavior
Mage should start like it does when the compose defines volumes instead of bind mounts.
Screenshots
The text was updated successfully, but these errors were encountered: