version: '3'
services:
db:
image: "mysql:5.7"
volumes:
- data-mysql:/var/lib/mysql
ports:
- '3306:3306'
environment:
MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
volumes:
data-mysql:
driver: local
Thank you Manny
There is no need for an env file. If you use only the variable name in the docker compose environment definition, its value will automatically be transferred from your host to the container:
services:
db:
image: "mysql:5.7"
ports: ['3306:3306']
environment:
MYSQL_ROOT_PASSWORD:
From the documentation:
Environment variables with only a key are resolved to their values on the machine Compose is running on, which can be helpful for secret or host-specific values.
If for some reason, you want or need to use an env file, you also can:
services:
db:
image: "mysql:5.7"
ports: ['3306:3306']
env_file:
- production.env
and in your production.env file (or whatever you name it), just put lines of key=value:
MYSQL_ROOT_PASSWORD=7op-s3cr37
See also The “env_file” configuration option.
docker container inspect, they can also docker run a container with unrestricted root-level access to the host filesystem. I'd make sure sudo access is required to run any docker command and limit who has access to that.