I searched the internet no good answer was found anywhere. When I run docker-compose up, down, or any command I am having this error.
cannot update snap namespace: cannot create symlink in "/etc/docker": existing file in the way
snap-update-ns failed with code 1
It was working fine, suddenly having this issue.
My OS is Ubuntu 20.04 docker version 20.10.8
Any kind of help is appreciated.
If you have not install the docker, you may run:
sudo snap install docker # version 20.10.8, or
Otherwise:
sudo apt install docker-compose # version 1.25.0-1
Hoping that this will help you!
Related
I have been struggling with the issue of "docker" command not being recognized in Windows cmd. I have docker installed on Windows Pro, and it is running ok, but the "docker" command is not recognized though the PATH variable contain the location of the docker binaries.
Any ideas on this, please? I have been looking everywhere, but could not find a solution!
Thanks.
I encontered the same problem. In my case (linux) it was because of broken installations. I've ran sudo apt --fix-broken install && sudo apt install docker-ce docker-ce-cli containerd.io
(Windows): I did not use my PC for a year, and got the same error after running docker --version. I just upgraded to the latest docker version, and issue resolved.
I updated docker desktop for Mac (intel) this morning to Docker Desktop 4.9.1. My docker compose version won't seem to update. When I run docker-compose --version in my terminal it returns docker-compose version 1.25.5, build unknown. I tried installing docker-compose with brew and after some tinkering I got confirmation that it installed version 2.6.0, however after restarting docker desktop and my computer, I still get 1.25.5 when I run docker-compose --version.
How can I force docker to use a newer version of docker-compose?
NOTE: In my docker-compose.yml file I have version 2 running.
My docker compose also came via Docker Desktop on MacOS and it did not update/had the latest the latest version of docker-compose. I resolved this by installing docker-compose via brew:
https://formulae.brew.sh/formula/docker-compose
brew install docker-compose
Don't forget to follow the after-install instructions:
"Compose is now a Docker plugin. For Docker to find this plugin, symlink it:"
mkdir -p ~/.docker/cli-plugins
ln -sfn /opt/homebrew/opt/docker-compose/bin/docker-compose ~/.docker/cli-plugins/docker-compose
The only way I was able to solve this was to completely manually uninstall docker desktop and all docker related items from brew. I deleted every docker file I could find from my lib and then reinstalled.
When running the following command docker-compose -f ./docker-compose-frontend.yml --env-file .env up I get the following error "Define and run multi-container applications with Docker" which provides no further guidance.
Installed on the system is Docker 20.10.7 and docker-compose 1.18.0.
yml files specify version number 3.3 which should be suitable with this version of compose so I'm not really sure what the issue is.
Any suggestions on things to try would be great as I am now just scratching my head on this one.
use sudo apt install docker-compose-plugin -y then try to install again
I am trying to upgrade to docker 1.9 from docker 1.8 version
I have used the following command to upgrade docker:
sudo wget https://get.docker.com/builds/Linux/x86_64/docker-latest -O
/usr/bin/docker
Howerver, after successful upgrade I am not able to restart the docker service.
The following command is failing
sudo systemctl start docker
Please help
It seems your disk is full. Check the disks df -h. And prepare enough disk space for your apps
After creating a new machine with Docker Machine, I'm getting the following error:
$ docker ps
Error response from daemon: client is newer than server(client API version 1.21, server API version: 1.19)
How can I fix this?
docker-machine upgrade <your-machine>
will do the trick. This can happen - as it did for me - even if you're not using RCs and your machine was newly created. It would be due to an ISO cache issue. The error is commented in this thread.
If the docker client is 1.9.x and the server is running docker 1.8.x,
the error message is observed.
If someone happens to get this error, but is not using docker-machine, there is another way to resolve the issue by specifying an older API version in an environment variable on the client side:
export DOCKER_API_VERSION=<version>
for example:
export DOCKER_API_VERSION=1.19
and retrying the docker command.
Reference.
On ubuntu distrib it happens after an apt update, if docker run as a service.
The client is updated but the old version of the server is still running.
In this case just do a:
sudo service docker restart
If you upgrade your docker client you will not be able to use old docker-machine VMs. Actually you can force an upgrade with docker-machine upgrade vm-name, but if you are working with other distros (except boot2docker) as docker host like coreos, atomic, rancheros it may fail.
I am using Carina to manage more than one docker client version.
just install with $ curl -sL https://download.getcarina.com/dvm/latest/install.sh | sh
(linux and mac installation) and run dvm ls to list installed versions, dvm install 1.9.0 to install versions and dvm use 1.8.1 to change your client version.
Very easy and powerfull. =)
Atention, for your safety always take a look inside scripts downloaded from internet before running them.
Hope it helps
Apparently this error is due to docker-machine "falling asleep". Here is the magic command solving it for me:
$ docker-machine restart default
Or replace default by the name of your machine.
The result is:
$ docker-machine restart default
Restarting "default"...
Restarted machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
As suggested, you may need to:
$ docker-machine env default
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://....."
export DOCKER_CERT_PATH=".../.docker/machine/machines/default"
export DOCKER_MACHINE_NAME="default"
# Run this command to configure your shell:
# eval $(docker-machine env default)
And so you finally run that command:
$ eval $(docker-machine env default)
From now it should work.
I had the same issue with 1.10.0-rc4, and it turned out that boot2docker wasn't updated properly when installing a newer Docker Toolbox. I had to remove boot2docker manually:
sudo rm -rf /usr/local/share/boot2docker
You can also delete the rest of the toolbox:
sudo rm -rf /usr/local/bin/docker*
sudo rm -rf /Applications/Docker
And finally install Docker Toolbox of the desired version.
Please see official uninstall script for on GitHub for OS X here.