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
The Ubuntu package docker actually refers to a GUI application, not the beloved DevOps tool we’ve come out to look for. The instructions for docker can be followed per instructions on the docker page here: https://docs.docker.com/engine/install/ubuntu/ === UPDATED (thanks @Scott Stensland) === You now run the following install script to get docker: sudo curl -sSL … Read more
I had the same issue on Ubuntu 17.04. This solution worked for me: sudo apt remove cmdtest sudo apt remove yarn curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add – echo “deb https://dl.yarnpkg.com/debian/ stable main” | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt-get update sudo apt-get install yarn -y then yarn install result: yarn install v1.3.2 warning You … Read more
It is because there is no package cache in the image, you need to run: apt-get update before installing packages, and if your command is in a Dockerfile, you’ll then need: apt-get -y install curl To suppress the standard output from a command use -qq. E.g. apt-get -qq -y install curl
You can try out this: systemctl start docker It worked fine for me. P.S.: after if there is commands that you can’t do without sudo, try this: gpasswd -a $USER docker
As mentioned in the comments, starting with Ubuntu 18.04 and Linux Mint Tara you need to first sudo apt install qemu-kvm. To check the ownership of /dev/kvm use ls -al /dev/kvm The user was root, the group kvm. To check which users are in the kvm group, use grep kvm /etc/group This returned kvm:x:some_number: on … Read more