Docker Compose with one Terminating Container

I’m having a docker compose setup of a database container, an application container and one container which pre-loads the database with necessary data.

I want to start all of the containers together with docker-compose up while the pre-loading container terminates after it is one with exit 0.

  • How much memory needed for build docker v1.9.0
  • Connecting to mongo container using node getting MongoError
  • Docker - How can i find running container?
  • There is a circular dependency in the target dependency graph involving target “DockerBuildServiceReferences”
  • docker build is very slow even with simple commands
  • autoexpect on docker centos6.6 container cannot work
  • But terminating this one container takes down the complete setup with the message:

    composesetup_load_1 exited with code 0
    Gracefully stopping... (press Ctrl+C again to force)
    Stopping composesetup_app_1...
    Stopping composesetup_db_1...

    Is there any way of having multiple containers with different life-time in one docker-compose setup? If yes, how?

  • Bind container port to host inside Dockerfile
  • Creating user in gerrit through ssh
  • Different file owner inside Docker container and in host machine
  • Can I build Docker contains for a Raspberry Pi on a AMD64 machine?
  • How to persist 'ln' in Docker with Ubuntu
  • unable to invoke docker container
  • One Solution collect form web for “Docker Compose with one Terminating Container”

    My workaround for now is to keep the pre-loading container running by adding tail -f /dev/null to the end of the entrypoint script. This keeps the process running, while nothing actual happens.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.