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.
Systemd “No such file or directory” itself during “docker-compose up”
Docker compose yml static IP addressing
compose extend file results in a validation error
hubot rocketchat adapter does not work
Docker compose lables constraint:node not work
is it possible to generate a random mysql password with dockercompose
Networking Docker Compose
How to change the config file for Riak TS when using Docker
Django Docker-compose machine does not start web server
How should docker-compose jobs discover etcd?
docker compose adding nodes dynamically to nginx frontend
Docker Swarm - dependencies definition
docker-compose volume not mounted
Exposing sentry service in docker-compose file
Yesod and docker-compose logs in development mode
Docker compose to always deploy using latest image