Prevent skip in docker-compose

I have a docker-compose.yml for a Django web app with a backend. It looks like this:

version: '2'

    image: # special image
      - "1433:1433"
      PASSWORD: "*********"

    build: .
    command: python runserver
      - "8000:8000"
      - db

When I run sudo docker-compose build, the first line of output says

  • Could not locate Gemfile error by docker compose up
  • GitLab Ci with docker runner - Multiple Stages
  • How do I register a new NuGet package source with dotnet CLI on Ubuntu 14.04?
  • docker automatically commit and push
  • Environment variables from env fiile in entrypoint in docker-compose.yml
  • fig docker monitoring broken container
  • db uses an image, skipping. 
    Building web.

    I need the db image to be built before web.

    How can I make the db image get built first?

  • Cannot get image on Docker - Network timed out [Windows]
  • Docker usage in compose/swarm mode
  • how to access docker registry v2 with curl?
  • deis-builder service have error when I provision Deis with Vagrant on CoreOS
  • Xvfb command in docker supervisor conf not working
  • pull from private docker repo in msbuild
  • One Solution collect form web for “Prevent skip in docker-compose”

    You can start your db container in Detached mode before building web:

    $ docker-compose up -d db
    $ docker-compose build web

    Though, this seems like an anti-pattern. I would recommended that you keep the build process for web as generic as possible, and instead use environment variables or command arguments to accomplish this.

    For instance, if you need to pass the same configuration values to both web and db, you could accomplish this using an env_file:

    # db_credentials.env

    And in your docker-compose.yml file:

        # ...
        env_file: db_credentials.env
        # ...
        env_file: db_credentials.env
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.