Difference between revisions of "Docker-compose up"
Jump to navigation
Jump to search
↑ https://docs.docker.com/compose/reference/up/
Line 6: | Line 6: | ||
https://docs.docker.com/compose/reference/up/ | 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. | 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. | ||
+ | |||
+ | |||
+ | == Examples == | ||
+ | * Upgrade a continer: <code>docker compose pull && docker-compose up -d</code> | ||
+ | |||
+ | |||
+ | |||
Revision as of 18:20, 12 January 2020
docker-compose up
[1] Builds, (re)creates, starts, and attaches to containers for a service.
docker-compose up -d
-d daemon
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.
Examples
- Upgrade a continer:
docker compose pull && docker-compose up -d
Related commands
See also
docker-compose
,docker-compose.yml
: [services
|volumes
|networks
|up
|down
|restart
|logs
|create
|changelog
|version
|secrets
|config
|-v
|-h
|exec], docker-compose pull
,Environment:
, Docker-compose.yml examples,.env
, release notes, expose:
Advertising: