You also need to install Docker Compose. See the manual. Here are the commands you need to execute sudo curl -L “https://github.com/docker/compose/releases/download/1.26.0/docker-compose-$(uname -s)-$(uname -m)” -o /usr/local/bin/docker-compose sudo mv /usr/local/bin/docker-compose /usr/bin/docker-compose sudo chmod +x /usr/bin/docker-compose
The following only builds the images, does not start the containers: docker-compose build The following builds the images if the images do not exist and starts the containers: docker-compose up If you add the –build option, it is forced to build the images even when not needed: docker-compose up –build The following skips the image … Read more
As of Docker 1.9, You are looking for –build-arg and the ARG instruction. Check out this document for reference. This will allow you to add ARG arg to the Dockerfile and then build with docker build –build-arg arg=2.3 .
In your case it was some other process that was using the port and as indicated in the comments, sudo netstat -pna | grep 3000 helped you in solving the problem. While in other cases (I myself encountered it many times) it mostly is the same container running at some other instance. In that case … Read more
Simple solution for me: sudo docker-compose up UPDATE 2016-3-14: At some point in the docker install process (or docker-compose ?) there is a suggestion and example to add your username to the “docker” group. This allows you to avoid needing “sudo” before all docker commands, like so: ~ > docker run -it ubuntu /bin/bash root@665d1ea76b8d:/# … Read more
Docker uses /var/lib/docker to store your images, containers, and local named volumes. Deleting this can result in data loss and possibly stop the engine from running. The overlay2 subdirectory specifically contains the various filesystem layers for images and containers. To cleanup unused containers and images, see docker system prune. There are also options to remove … Read more
I had experienced this issue after upgrading to the latest Docker Desktop version on Mac. Solved with the comment on this issue. Solution: Don’t use buildkit and it works for me. export DOCKER_BUILDKIT=0 export COMPOSE_DOCKER_CLI_BUILD=0
The command clause does work as @Karthik says above. As a simple example, the following service will have a -inMemory added to its ENTRYPOINT when docker-compose up is run. version: ‘2’ services: local-dynamo: build: local-dynamo image: spud/dynamo command: -inMemory
This happens because you have added your worker directory as a volume to your docker-compose.yml, as the volume is not mounted during the build. When docker builds the image, the node_modules directory is created within the worker directory, and all the dependencies are installed there. Then on runtime the worker directory from outside docker is … Read more
I’ve seen it suggested docker may be at its maximum of created networks. The command docker network prune can be used to remove all networks not used by at least one container. My issue ended up being, as Robert commented about: an issue with openvpn service openvpn stop ‘solved’ the problem.