Exited (100) with ENV LANG

[robertogyn19]

The container does not start when configure env LANG="en-US.UTF-8".

$ docker run -d -e "LANG=en_US.UTF-8" --name mongodb dockerfile/mongodb
$ docker ps -a
CONTAINER ID        IMAGE                                               COMMAND                CREATED             STATUS                        PORTS               NAMES
ea6e30400da3        dockerfile/mongodb:latest                           "mongod"               2 seconds ago       Exited (100) 2 seconds ago                        mongodb

$ docker version
Client version: 1.2.0
Client API version: 1.14
Go version (client): go1.3.1
Git commit (client): fa7b24f
OS/Arch (client): linux/amd64
Server version: 1.2.0
Server API version: 1.14
Go version (server): go1.3.1
Git commit (server): fa7b24f

$ docker images dockerfile/mongodb
REPOSITORY           TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
dockerfile/mongodb   latest              a0775ca89ae7        2 hours ago         710.7 MB

[jtmarmon]

@pilwon any idea about this? I'm getting exit code 100 without any env variables (run command is sudo docker run -d -p 27017:27017 --name=mongo dockerfile/mongodb)

[immutef]

same here, container always exits with code 100 :(

[jeremy6d]

same here, the image used to work but now I'm getting exits w/ code 100

[jaydp17]

May be it's because of Insufficient free space for journal files. It may not be the case for everyone, but freeing up some space worked for me

[jtmarmon]

^ i believe my solution to this was running with --smallFiles

[sunao-uehara]

Same issue here. --smallFiles doesn't fix this issue for me. Anybody still having issue?

my docker-compose.yml file is like this

database:
  image: mongo:2.6
  command: "--smallfiles"
  volumes:
    - data/mongodb:/data/db
  ports:
    - "27017:27017"

[agamrafaeli]

For me the problem was that I shut down my computer without shutting down the container properly.

When starting the container an internal problem happened with the mongo. I SSH'ed into the machine and deleted a lock file and then the container started all right for me.

[Secbone]

same here, docker run is ok but exits with code 100 with docker-compose :(

[panneerboss]

work around available - https://github.com/docker-library/mongo/issues/74

[jovanialferez]

thanks @m-amr! works for me.

[m-amr]

@jovanialferez I think it is not working as expected if you try to open data/db you will found it empty. please check it ? I have deleted my solution because it is not working as expected.

[jovanialferez]

@m-amr yes, it works.. it created data/mongo on my host (windows 10 pro) which maps to data/db inside the container which is not empty in my case.

[jovanialferez]

@m-amr here is a snippet from my docker-compose.yml file:

mongo:
    image: mongo:latest
    ports:
        - "27017:27017"

mongoclient: 
    image: mongoclient/mongoclient
    ports:
        - "3000:3000"
volumes_data:
    image: tianon/true
    volumes:
        - ./data:/data

[m-amr]

@jovanialferez but the db directory is empty ? can you check it ?

[jovanialferez]

@m-amr the db directory inside the container is not empty.

[jovanialferez]

@m-amr some files inside the container isnt visible in the host though.

[alex1012]

@m-amr i have same problem, this solution is not working for me =(

[natesire]

Is there a way to tell docker or mongodb to exit with a more useful message than just the error code 100. That code could mean a plethora of problems. Unfortunately the docker and mongodb logs are empty.