Why do volumes in docker-compose rub the directory inside the container?

[impkos (Ruslan)]

version: ‘3’

services:
web:
image: test/vitrina_20:$VITRINA_RELEASE
command: [’./init.sh’]
volumes:

• /var/www/html/vitrina_20/static:/code/static

ports:

• “8001:8000”
  environment:
• DATANRM_URL
• DATANRM_USER
• DATANRM_PASS

There is a docker-compose file.

1. Why does the contents of the static folder inside the container get erased when I run the docker-compose.yml file?
2. How to make the contents of the / code / static folder as it exists in the container was forwarded to the / var / www / html / vitrina_20 / static folder on the host system?

[nitishmowall]

hey @impkos
please check this thread

Why docker-compose down deletes my volume? how to define volume as external?

I use docker in ubuntu 16.04 LTS: Docker version 18.06.1-ce, build e68fc7a in https://docs.docker.com/compose/reference/down/ it stated that docker-compose down by default doesn’t remove volumes. mongo: image: mongo restart: always networks: - mynetwork environment: MONGO_INITDB_ROOT_USERNAME: user MONGO_INITDB_ROOT_PASSWORD: pass volumes: - ./mongodata:/db/data when I run docker-compose down without -v or --volumes, why my data is lost? does docker delete my volume? it’s already…

[tekki]

@impkos

volumes:
- /var/www/html/vitrina_20/static:/code/static

1. Why does the contents of the static folder inside the container get erased

I don’t think it gets erased, it just gets invisible because you mount another drive into /code/static. If you need this content on your external folder it should be located at another place in the container. Then you can add an entrypoint script that copies or rsyncs it to the volume on startup.