Skip to content
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

Exit code 100 #18

Closed
jtmarmon opened this issue Jan 15, 2015 · 9 comments
Closed

Exit code 100 #18

jtmarmon opened this issue Jan 15, 2015 · 9 comments

Comments

@jtmarmon
Copy link

My container is automatically exiting with error code 100 after sudo docker run -d -p 27017:27017 --name=mongo mongo.

OS stats:

NAME="Amazon Linux AMI"
VERSION="2014.09"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2014.09"
PRETTY_NAME="Amazon Linux AMI 2014.09"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2014.09:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
@jtmarmon
Copy link
Author

ah, this is resolved via the --smallfiles option

@unoexperto
Copy link

Sadly it didn't help me. Any other options guys ? I run it via

docker run -p 127.0.0.1:27017:27017 --name mymongo -d mongo:3.1.6 --smallfiles

@MattMoranJava
Copy link

Doesn't work for me either. Trying to run mongodb docker container in Windows 10. I'm using:
docker run --name mongodb_svcrm -p 27017:27017 -v C:\Users\matt.moran\Documents\myproject\data\db:/data/db -d mongo --smallfiles
docker ps -a shows it exits with code 100. There's plenty of disk space in the host system for journals.
Any idea why this is happening?

@yosifkit
Copy link
Member

@MattMoranJava for Docker on Windows, see #107 (comment)

@m-amr
Copy link

m-amr commented Aug 20, 2017

try to make the whole data directory as a volume
instead of

volumes:
- ./data/db:/data/db

try
volumes:
- ./data:/data

it works for me.

@tianon
Copy link
Member

tianon commented Aug 21, 2017

Since the Dockerfile defines a volume on /data/db, if you only mount /data you will not be keeping your data. If you check our data folder on your host, you'll see that it has a db subdirectory, but it should be empty, because it's in a separate volume.

@m-amr
Copy link

m-amr commented Aug 21, 2017

@tianon you are right this doesn't solve the problem.

@aorlenko
Copy link

So are there any solutions to this? Should directory mounting work with mongo:windowsservercore image?

@yosifkit
Copy link
Member

@aorlenko, current solutions are to mount a folder from the VM (#74 (comment)) or use a named volume (#74 (comment)).

Yes, the windowsservercore images work just fine if you are using windows containers:

PS C:\Users\Docker\docker> docker run -d --name mongo -v C:\Users\Docker\docker\mongo-data:C:\data\db mongo:3.4-windowsservercore
PS C:\Users\Docker\docker> ls .\mongo-data\


    Directory: C:\Users\Docker\docker\mongo-data


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        9/13/2017   2:30 PM                diagnostic.data
d-----        9/13/2017   2:30 PM                journal
-a----        9/13/2017   2:30 PM          16384 collection-0--6462546833303440715.wt
-a----        9/13/2017   2:30 PM          16384 collection-2--6462546833303440715.wt
-a----        9/13/2017   2:30 PM          16384 index-1--6462546833303440715.wt
-a----        9/13/2017   2:30 PM          16384 index-3--6462546833303440715.wt
-a----        9/13/2017   2:30 PM          16384 index-4--6462546833303440715.wt
-a----        9/13/2017   2:30 PM              0 mongod.lock
-a----        9/13/2017   2:30 PM          16384 sizeStorer.wt
-a----        9/13/2017   2:30 PM             95 storage.bson
-a----        9/13/2017   2:30 PM             49 WiredTiger
-a----        9/13/2017   2:30 PM             21 WiredTiger.lock
-a----        9/13/2017   2:30 PM            986 WiredTiger.turtle
-a----        9/13/2017   2:30 PM          24576 WiredTiger.wt
-a----        9/13/2017   2:30 PM           4096 WiredTigerLAS.wt
-a----        9/13/2017   2:30 PM          16384 _mdb_catalog.wt


PS C:\Users\Docker\docker>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants