What does working_dir tag mean in a docker-compose yml file
Just wondering what the working_dir file really does for an image being loaded via docker-compose. A sample docker-compose.yml file as follows: dev: extends: file: common.yml service: workspace volumes: - $ATOMSPACE_SOURCE_DIR:/atomspace - $COGUTILS_SOURCE_DIR:/cogutils # Uncomment the following lines if you want to work on moses # - $MOSES_SOURCE_DIR:/moses working_dir: /opencog # This is the same as the volume mount point below links: - postgres:db - relex:relex postgres: image: opencog/postgres # Uncomment the following lines if you want to work on a production # system. # NOTE: The environment variable `PROD` is set `True` then the entrypoint # script in opencog/postgres does additional configurations. # environment: # - PROD=True relex: image: opencog/relex command: /bin/sh -c "./opencog-server.sh"
working_dir sets the working directory of the container that is created. It is the same as the --workdir flag to docker run.
How to work out the hostname that compose gives containers?
docker-compose restart container if service is dead
Swarm scheduling not working as expected using filters in compose file
issues in buiding Slate with Docker
Invalid type error in Docker Compose
Django cookiecutter with Docker add pip package
Docker Compose + Swarm + Machine Networking issue
docker-compose build image parameters --force-rm --pull
linking 2 containers through docker compose
Files created by manage.py commands not chown'd from root user
Is it possible to create an intermediate image within docker-compose?
docker-compose service listen on specified interface
Does Docker-Compose allow overwriting of ports when using extends?
Jhipster Docker-compose conflict
Build multiple images with Docker Compose?
JHipster Cassandra Docker Build