Difference between revisions of "Docker-compose up"

From wikieduonline
Jump to navigation Jump to search
Line 52: Line 52:
 
* <code>[[docker-compose logs]]</code>
 
* <code>[[docker-compose logs]]</code>
 
* <code>[[docker-compose pull]]</code>
 
* <code>[[docker-compose pull]]</code>
 +
* [[Docker-compose.yml examples]]
  
 
== See also ==
 
== See also ==

Revision as of 06:06, 1 July 2020

https://docs.docker.com/compose/reference/up/


  • docker-compose up -d
-d daemon

[1] Builds, (re)creates, starts, and attaches to containers for a service.



https://docs.docker.com/compose/reference/up/ If there are existing containers for a service, and the service’s configuration or image was changed after the container’s creation, docker-compose up picks up the changes by stopping and recreating the containers (preserving mounted volumes). To prevent Compose from picking up changes, use the --no-recreate flag.

docker-compose up, and docker-compose start will now start containers in parallel where possible.


Examples

  • docker-compose up
  • docker-compose up SERVICE_NAME
docker-compose up -d
Recreating SERVICE_NAME... done
  • Build containers but do not start them:
docker-compose up --no-start
  • Upgrade a container:
docker-compose pull && docker-compose up -d


docker-compose up -d SERVICE_NAME
Creating volume "VOLUME_NAME" with default driver
Creating SERVICE_NAME ... done
  • Using specific docker compose file:
docker-compose -f NAME_OF_YOUR_FILE up

Examples with errors

docker-compose up
ERROR: The Compose file is invalid because:
Service SERVICE_NAME has neither an image nor a build context specified. At least one must be provided.
docker-compose up
ERROR: yaml.parser.ParserError: while parsing a block mapping
 in "./docker-compose.yml", line 1, column 1
expected <block end>, but found '<block mapping start>'
 in "./docker-compose.yml", line 3, column 2

Related commands

See also

  • https://docs.docker.com/compose/reference/up/
  • Advertising: