Difference between revisions of "Docker-compose up"
Jump to navigation
Jump to search
↑ https://docs.docker.com/compose/reference/up/
Line 57: | Line 57: | ||
ERROR: build path /srv/mattermost/db either does not exist, is not accessible, or is not a valid URL. | ERROR: build path /srv/mattermost/db either does not exist, is not accessible, or is not a valid URL. | ||
Solution: <code>[[git clone]] https://github.com/mattermost/mattermost-docker.git</code> | Solution: <code>[[git clone]] https://github.com/mattermost/mattermost-docker.git</code> | ||
+ | |||
+ | docker-compose up | ||
+ | ERROR: | ||
+ | Can't find a suitable configuration file in this directory or any | ||
+ | parent. Are you in the right directory? | ||
+ | |||
+ | Supported filenames: [[docker-compose.yml]], [[docker-compose.yaml]], [[compose.yml]], [[compose.yaml]] | ||
== Related commands == | == Related commands == |
Revision as of 22:16, 4 July 2022
docker-compose
builds, (re)creates, starts, and attaches to containers for a service.
-d daemon
docker-compose up --help
docker-compose up
docker-compose up --timeout 600
docker-compose up SERVICE_NAME
docker-compose up -d SERVICE_NAME
docker-compose -f NAME_OF_YOUR_FILE up
[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
docker-compose up
ERROR: build path /srv/mattermost/db either does not exist, is not accessible, or is not a valid URL.
Solution: git clone https://github.com/mattermost/mattermost-docker.git
docker-compose up ERROR: Can't find a suitable configuration file in this directory or any parent. Are you in the right directory?
Supported filenames: docker-compose.yml, docker-compose.yaml, compose.yml, compose.yaml
Related commands
docker-compose
: [start
|stop
|restart
|pull
|up
|down
|ps
]docker-compose logs
docker-compose pull
- Docker-compose.yml examples
docker-compose down && docker-compose build --pull && docker-compose up -d
docker image ls
See also
docker-compose
: [start
|stop
|restart
|pull
|up
|down
|ps
]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-compose --env-file,services.deploy.resources
Advertising: