Difference between revisions of "Docker-compose up"
Jump to navigation
Jump to search
↑ https://docs.docker.com/compose/reference/up/
| Line 14: | Line 14: | ||
* <code>[[docker-compose pull]]</code> | * <code>[[docker-compose pull]]</code> | ||
* <code>[[docker-compose down]]</code> | * <code>[[docker-compose down]]</code> | ||
| + | * <code>[[docker-compose start]]</code> | ||
== See also == | == See also == | ||
Revision as of 13:53, 18 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 container:
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:- Docker:
docker-compose, Docker Desktop, Docker Scout, Docker Swarm, Docker Volumes, Docker images management, docker network,docker inspect,docker volume inspect,Dockerfile, Docker Engine release notes,docker kill,moby, Docker-in-Docker,docker context,buildx,docker tag,docker system prune, Docker Hub,hub-tool, /etc/docker/daemon.json,hostconfig.json, dockerd, logs, Docker logging, Backup,docker service,depends on,--dns, --filter,--mount,docker login,docker build,apt remove docker.io,.dockerignore, docker context ls |docker-machine, .docker/, PWD,$HOME/.docker/config.json, Docker ID,--env-file, docker --help
Advertising:
