Using Docker-Compose how to execute multiple commands

Question

I want to do something like this where I can run multiple commands in order  db    image  postgres web    build      command  python manage py migrate   command  python manage py runserver 0 0 0 0 8000   volumes      -    code   ports      -  quot 8000 8000 quot    links      - db

User · Answer

Another idea   If  as in this case  you build the container just place a startup script in it and run this with command  Or mount the startup script as volume

User · Answer

You can use entrypoint here  entrypoint in docker is executed before the command while command is the default command that should be run when container starts  So most of the applications generally carry setup procedure in entrypoint file and in the last they allow command to run   make a shell script file may be as docker-entrypoint sh  name does not matter  with following contents in it      bin bash python manage py migrate exec        in docker-compose yml file use it with entrypoint   docker-entrypoint sh and register command as command  python manage py runserver 0 0 0 0 8000 P S   do not forget to copy docker-entrypoint sh along with your code

User · Answer

If you need to run more than one daemon process  there s a suggestion in the Docker documentation to use Supervisord in an un-detached mode so all the sub-daemons will output to the stdout   From another SO question  I discovered you can redirect the child processes output to the stdout   That way you can see all the output

User · Answer

To run multiple commands in the docker-compose file by using bash -c   command   gt      bash -c  python manage py makemigrations      amp  amp  python manage py migrate      amp  amp  python manage py runserver 0 0 0 0 8000    Source  https   intellipaat com community 19590 docker-run-multiple-commands-using-docker-compose-at-once show 19597 a19597

User · Answer

I ran into this while trying to get my jenkins container set up to build docker containers as the jenkins user   I needed to touch the docker sock file in the Dockerfile as i link it later on in the docker-compose file   Unless i touch ed it first  it didn t yet exist   This worked for me   Dockerfile   USER root RUN apt-get update  amp  amp    apt-get -y install apt-transport-https   ca-certificates   curl   software-properties-common  amp  amp    curl -fsSL https   download docker com linux      etc os-release   echo   ID   gpg  gt   tmp dkey  apt-key add  tmp dkey  amp  amp    add-apt-repository    deb  arch amd64  https   download docker com linux      etc os-release  echo   ID       lsb release -cs    stable   amp  amp    apt-get update  amp  amp    apt-get -y install docker-ce RUN groupmod -g 492 docker  amp  amp    usermod -aG docker jenkins   amp  amp    touch  var run docker sock  amp  amp    chmod 777  var run docker sock  USER Jenkins   docker-compose yml   version   3 3  services  jenkins pipeline      build        ports        -  8083 8083        -  50083 50080      volumes          -  root pipeline jenkins mount point home  var jenkins home         -  var run docker sock  var run docker sock

User · Answer

I was having same problem where I wanted to run my react app on port 3000 and storybook on port 6006 both in the same containers  I tried to start both as entrypoint commands from Dockerfile as well as using docker-compose command option  After spending time on this  decided to separate these services into separate containers and it worked like charm

User · Answer

Cleanest   --- version   quot 2 quot  services    test      image  alpine     entrypoint    quot  bin sh quot   quot -c quot       command      -          echo a        echo b        echo c

User · Answer

UPDATE    I figured the best way to run some commands is to write a custom Dockerfile that does everything I want before the official CMD is ran from the image   docker-compose yaml   version   3     Can be used as an alternative to VBox Vagrant services     mongo      container name  mongo     image  mongo     build        context          dockerfile  deploy local Dockerfile mongo     ports        -  27017 27017      volumes        -     data mongodb  data db   Dockerfile mongo   FROM mongo 3 2 12  RUN mkdir -p  fixtures  COPY   fixtures  fixtures  RUN  mongod --fork --syslog  amp  amp         mongoimport --db wcm-local --collection clients --file  fixtures clients json  amp  amp         mongoimport --db wcm-local --collection configs --file  fixtures configs json  amp  amp         mongoimport --db wcm-local --collection content --file  fixtures content json  amp  amp         mongoimport --db wcm-local --collection licenses --file  fixtures licenses json  amp  amp         mongoimport --db wcm-local --collection lists --file  fixtures lists json  amp  amp         mongoimport --db wcm-local --collection properties --file  fixtures properties json  amp  amp         mongoimport --db wcm-local --collection videos --file  fixtures videos json    This is probably the cleanest way to do it     OLD WAY    I created a shell script with my commands  In this case I wanted to start mongod  and run mongoimport but calling mongod blocks you from running the rest    docker-compose yaml   version   3   services    mongo      container name  mongo     image  mongo 3 2 12     ports        -  27017 27017      volumes        -   fixtures  fixtures       -   deploy  deploy       -     data mongodb  data db     command  sh  deploy local start mongod sh   start mongod sh   mongod --fork --syslog  amp  amp    mongoimport --db wcm-local --collection clients --file  fixtures clients json  amp  amp    mongoimport --db wcm-local --collection configs --file  fixtures configs json  amp  amp    mongoimport --db wcm-local --collection content --file  fixtures content json  amp  amp    mongoimport --db wcm-local --collection licenses --file  fixtures licenses json  amp  amp    mongoimport --db wcm-local --collection lists --file  fixtures lists json  amp  amp    mongoimport --db wcm-local --collection properties --file  fixtures properties json  amp  amp    mongoimport --db wcm-local --collection videos --file  fixtures videos json  amp  amp    pkill -f mongod  amp  amp    sleep 2  amp  amp    mongod   So this forks mongo  does monogimport and then kills the forked mongo which is detached  and starts it up again without detaching  Not sure if there is a way to attach to a forked process but this does work   NOTE  If you strictly want to load some initial db data this is the way to do it   mongo import sh     bin bash   Import from fixtures    Used in build and docker-compose mongo  different dirs  DIRECTORY    deploy local mongo fixtures if    -d   fixtures      then     DIRECTORY  fixtures fi echo   DIRECTORY   mongoimport --db wcm-local --collection clients --file   DIRECTORY  clients json  amp  amp    mongoimport --db wcm-local --collection configs --file   DIRECTORY  configs json  amp  amp    mongoimport --db wcm-local --collection content --file   DIRECTORY  content json  amp  amp    mongoimport --db wcm-local --collection licenses --file   DIRECTORY  licenses json  amp  amp    mongoimport --db wcm-local --collection lists --file   DIRECTORY  lists json  amp  amp    mongoimport --db wcm-local --collection properties --file   DIRECTORY  properties json  amp  amp    mongoimport --db wcm-local --collection videos --file   DIRECTORY  videos json   mongo fixtures   json files were created via mongoexport command   docker-compose yaml  version   3   services    mongo      container name  mongo     image  mongo 3 2 12     ports        -  27017 27017      volumes        - mongo-data  data db cached       -   deploy local mongo fixtures  fixtures       -   deploy local mongo import sh  docker-entrypoint-initdb d mongo import sh   volumes    mongo-data      driver  local

User · Answer

I recommend using sh as opposed to bash because it is more readily available on most Unix based images  alpine  etc   Here is an example docker-compose yml  version   3   services    app      build        context        command   gt        sh -c  quot python manage py wait for db  amp  amp               python manage py migrate  amp  amp               python manage py runserver 0 0 0 0 8000 quot   This will call the following commands in order   python manage py wait for db - wait for the DB to be ready python manage py migrate - run any migrations python manage py runserver 0 0 0 0 8000 - start my development server

User · Answer

I run pre-startup stuff like migrations in a separate ephemeral container  like so  note  compose file has to be of version  2  type   db    image  postgres web    image  app   command  python manage py runserver 0 0 0 0 8000   volumes      -    code   ports      -  quot 8000 8000 quot    links      - db   depends on      - migration migration    build      image  app   command  python manage py migrate   volumes      -    code   links      - db   depends on      - db  This helps things keeping clean and separate  Two things to consider   You have to ensure the correct startup sequence  using depends on    You want to avoid multiple builds which is achieved by tagging it the first time round using build and image  you can refer to image in other containers then

User · Answer

This works for me  version   3 1  services    db      image  postgres   web      build        command        -  bin bash       - -c       -           python manage py migrate         python manage py runserver 0 0 0 0 8000      volumes        -    code     ports        -  quot 8000 8000 quot      links        - db  docker-compose tries to dereference variables before running the command  so if you want bash to handle variables you ll need to escape the dollar-signs by doubling them        command        -  bin bash       - -c       -           var    echo  foo           echo   var   prints foo     otherwise you ll get an error   Invalid interpolation format for  quot command quot  option in service  quot web quot

User · Answer

Alpine-based images actually seem to have no bash installed  but you can use sh or ash which link to  bin busybox  Example docker-compose yml  version   quot 3 quot  services     api      restart  unless-stopped     command  ash -c  quot flask models init  amp  amp  flask run quot

User · Answer

Use a tool such as wait-for-it or dockerize  These are small wrapper scripts which you can include in your application   s image  Or write your own wrapper script to perform a more application-specific commands  according to  https   docs docker com compose startup-order

User · Answer

There are many great answers in this thread already  however  I found that a combination of a few of them seemed to work best  especially for Debian based users  services    db               web                depends on         -  quot db quot      command   gt              bash -c  quot   wait-for-it sh db 5432 -- python manage py makemigrations        amp  amp  python manage py migrate        amp  amp  python manage py runserver 0 0 0 0 8000 quot   Prerequisites  add wait-for-it sh to your project directory  Warning from the docs   quot  When using wait-for-it sh  in production  your database could become unavailable or move hosts at any time      This solution is for people that  don   t need this level of resilience  quot

User · Answer

Figured it out  use bash -c   Example   command  bash -c  python manage py migrate  amp  amp  python manage py runserver 0 0 0 0 8000    Same example in multilines   command   gt      bash -c  python manage py migrate      amp  amp  python manage py runserver 0 0 0 0 8000    Or   command  bash -c       python manage py migrate      amp  amp  python manage py runserver 0 0 0 0 8000

User · Answer

try using     to separate the commands if you are in verions two e g   command   sleep 20  echo  a

[docker] Using Docker-Compose, how to execute multiple commands

Examples related to docker

Examples related to yaml

Examples related to docker-compose