cpu-shares is a ‘relative weight’, relative to the default setting of 1024, so if you had two containers running on the same core, you could give them the CPU 50-50 or 80-20 or whatever you wanted by adjusting the numbers. It is an integer. You cannot give an overall limit, as you want to, using … Read more
try something like this – ${PWD}/:/var/www/html
What you are looking for is: eval “$(docker-machine env -u)” It will unset the DOCKER_* variables. For the record, here’s the output of docker-machine env -u: unset DOCKER_TLS_VERIFY unset DOCKER_HOST unset DOCKER_CERT_PATH unset DOCKER_MACHINE_NAME
The issue is that your DOCKER_HOST is not set to localhost, you will need to use the IP address of your docker-machine, since you are using Docker Toolbox: docker-machine ip default # should return your IP address. See Docker Toolbox Docs for more information.
In the future, you could use this website to check what is wrong with it and then fix it on the go. EDIT: So the problems you had with your docker-compose file were as follows: You didn’t added the services: keyword after the version and You don’t have to pass the :latest tag if you … Read more
Run the container typing -p option before the image name docker run –name rva-db -e POSTGRES_PASSWORD=rva -e POSTGRES_DB=rva-db -d -p 5432:5432 postgres As for Docker run reference docker run has this format docker run [OPTIONS] IMAGE[:TAG|@DIGEST] [COMMAND] [ARG…] Options must be before image name. After that you can set entrypoint or command (when theyy differ … Read more
Well there are a couple of problems. The first one is that those two containers (wordpress and wordpress-cli) don’t share a volume. So while wordpress has a wordpress installation ready, the wordpress-cli doesn’t. So you can add volumes to both containers, and then wordpress-cli will find the wordpress installation. Then there’s a second problem: the … Read more