Error with MongoDb image & volume mount
See original GitHub issueWhen starting the nanoserver MongoDB image with a volume I the container doesn’t start and I get a cryptic error
docker run --rm -it --mount source=myvol,target=c:/Data/db stefanscherer/mongo-windows:latest
docker: Error response from daemon: container
7c2a36d7fe3dcf608eb1b8afd16fcc4ad0573db464a5d5ad863d3cc0041b411c
encountered an error during CreateContainer: failure in a Windows system call: The request is not supported. (0x32)
<rest of message removed>
If I remove the volume mount it starts perfectly OK. I’m seeing this problem locally (Windows 10 - Docker Version 17.12.0-ce-win47 (15139)) and also when running the container in Azure
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Docker image: Error response from daemon: cannot mount ...
When you commit the container and try to relaunch it, it has some sort of record that something should be mounted there, and...
Read more >Issues with mongo with mounted volume for data
I've set up Docker to share the drive where my docker-compose file is located. My docker-compose: some-mongo: image: "mongo:latest" volumes:
Read more >Docker User Number - Ops and Admin - MongoDB
Hi, I am running mongodb using docker compose. Within the container the /data folder is owned by mongodb which is user number 999....
Read more >pods unable to access mounted volumes - Google Groups
It is set to the image not running with root privs. If you want a work around, i did an example with an...
Read more >MongoDB | Using Images | OpenShift Container Platform 3.11
If you do not specify all four, the pod will fail to start and OpenShift ... The MongoDB image can be run with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems like the
VOLUME C:\data\db
instruction makes problems with 1709. It leaves a container mapped directory link in the mongo image which then cannot be mounted with 1709 server at runtime.And the nanoserver image must be run with
-u ContainerAdministrator
to have access to the mounted volume. Weird.This Dockerfile seems to work building and running on a 1709 machine
FYI this container worked ok, thanks for your help and thanks for these images you are making available to the community. These have become the defacto images for things like Node and Mongo on Windows so thanks for your efforts