I cant start my docker in Linux mint - docker

[myshell]# sudo dockerd
Error starting daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid
In linux, I installed docker but daemon is not running.
the above given error is always generated.

Check If you already have the Docker Installed in it.
May be The Installation was not proper.
Check this Link

if you
cat /var/run/docker.pid
it is mostly likely you are already running it.
you can take a look at the official and proper way to launch your docker once it is installed
https://docs.docker.com/config/daemon/systemd/

Related

Windows equivalent for running this docker code

What is the windows equivalent of this code?
sudo docker pull ghcr.io/theislab/extended-single-cell-best-practices-container:latest
Link to docker
I have tried running this command already in windows cmd:
docker run ghcr.io/theislab/extended-single-cell-best-practices-container:latest
I can not reproduce your problem,
docker run ghcr.io/theislab/extended-single-cell-best-practices-container:latest
works fine for me. Without the error messages debugging will be impossible. I can just give some Assumptions.
Do you have docker desktop installed? if not -> Docker Desktop
Is the docker daemon running? to find out, try docker ps in the powershell. When the Answer to this is error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified., your daemon is probably not running -> Start docker desktop. The file to do so should be in a directory like this : C:\Program Files\Docker\Docker\Docker Desktop.exe
For further debugging I would need more information on the error Message. This kind of message would have been better as a comment, but I'm not allowed to write some because of my low reputation, sorry for that

IOTA "one-click-tangle" via docker linux containers - ERROR 1

I am trying to run a private tangle on my computer through linux docker containers.
Therefore I followed the guide over at https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle
Every step succeeded up until we tried to execute
./private_tangle.sh install
This reports
Error 1
as seen in the screenshot below:
We do net get any further information, is anyone familiar with this error, or has any clue how to get some more information on the error so that we can at least have a clue where to look?
Some further information:
After executing docker ps -a we see that not a single container is running.
I am running on a windows 10 machine
I execute the commands from within ubuntu (version 20.04)
Ubuntu, docker-desktop and docker-desktop-data are all running WSL2
Docker integration with ubuntu is activated
I thought the error could maybe come from no hornet node initially being installed, so I installed a hornet node successfully, according the guide that https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle. This changed nothing to the Error.
The version of docker and docker-compose are compliant with the requirements
If any more details are needed to help me solve this problem, please let me know.
I used the documentation (https://wiki.iota.org/chrysalis-docs/tutorials/one_click_private_tangle) to install these containers on my local ubuntu 18.04.
My docker version is: 20.10.12
And docker-compose version is: 1.29.2
By following the steps of the tutorial I managed to successfully start all of the containers without trouble.
My guess here would be that the permission of the 'private-tangle.sh' are not correct or that there is permission problem on the docker level.
You should start with checking the permission level of the private-tangle.sh script by using $ls -l
Here is my output -rwxrwxr-x 1 ben ben 9413 Jan 11 11:28 private-tangle.sh
It could also be due to the docker rights if you have to use sudo when executing a docker command it will give some troubles when executing the script.
You need to add yourself to a docker group to be able to run docker commands without sudo. You can do this by running sudo usermod -aG docker $USER with damiaan-vh as $user.
Solution from source https://stackoverflow.com/posts/70665394/edit
Suggesting to downgrade ubuntu version to 18.04 for more stable version.
For reinstalling the docker and docker-compose programs follow this documentations
(docker: https://docs.docker.com/engine/install/ubuntu/ )
(docker-compose: https://docs.docker.com/compose/install/ )

error during connect: The system cannot find the file specified..,the docker client must be run elevated to connect [duplicate]

System info:
Windows 10 pro 64 bit
C:\WINDOWS\system32>docker --version
Docker version 18.06.1-ce, build e68fc7a
C:\WINDOWS\system32>docker info
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
C:\WINDOWS\system32>docker pull hello-world
Using default tag: latest
Warning: failed to get default registry endpoint from daemon (error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.). Using system default: https://index.docker.io/v1/
error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/images/create?fromImage=hello-world&tag=latest: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
You can powerShell as admin.
Run this code:
cd "C:\Program Files\Docker\Docker"
./DockerCli.exe -SwitchDaemon
Running Powershell with elevated access solved my issue.
Usually this error means the Docker daemon that is docker services is not up and running.
Make sure docker is running by issuing below command in power shell in elevated mode.
docker run hello-world
A response as hello from docker will be printed on console.
Else start the docker by double clicking the docker app from start menu.
Below is the snapshot of graphically up and running docker daemon.
On Windows, go to the folder %homepath%\.docker, open daemon.json and if debug is set to true then set it to false.
I had the same error as in the question and after I changed the above it worked again for me. After I got the error, I had been looking at the various docker settings and decided to set debug to false because I don't need any daemon debug info for what I'm doing. I don't know why it was set to true originally.
In my case, although I had the docker service running as admin and the service was shown as running, it was not.
Open the docker desktop app, click on the 'troubleshoot' icon. Check if the service is effectively running (bottom left). If it's not, try to 'clean/purge data', and then restart the service. It worked for me!
Verify it by running docker run hello-world
Fow Windows:
Launch command: "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon
This error is because of organisation network certificates which are installed in local machine. Beacuse some companies restricted network by installing certificates.
docker daemon service is not running on my machine and when I start the service, this error us resolved.
I had faced the same error, the following worked for me:
In the windows taskbar, the docker icon was red in color saying Out of Memory...
In the Docker Desktop App, goto
Settings -> Resources -> Disk Image Size -> decrease the space allocated -> Apply & Restart
This did happen to me while i was using docker today for the first time. I fixed by opening up the docker app in the PC and signing and selecting the necessary subscription plan.
Open docker with docker <homepath>. Simply upgrade docker and then run this command
docker-compose up -d
you will be able to solve the specified path error.
docker.errors.DockerException: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.')
[14620] Failed to execute script docker-compose
Doing the above solved the error.
Yo,
open docker app > settings > Docker engine > "debug": true,
debug was false initially, after changing it to "true" it worked.
Thanks.

Docker Installation Problems

I'm new to using Docker (never used it before) and I'm running into these errors:
I installed the Docker for Windows and following the steps on this
tutorial, but Docker Desktop doesn't load up for me at all.
I tried to run the docker pull hello-world command but I'm getting the error: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
How do I fix this? Thanks

Docker now giving an error after updating

After using Docker for almost two months, today I got the following error:
C:\Users\dell>docker --version
Docker version 17.06.0-ce, build 02c1d87
C:\Users\dell>docker ps -a
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.30/containers/json?all=1:
open //./pipe/docker_engine: The system cannot find the file
specified. In the default daemon configuration on Windows, the docker
client must be run elevated to connect. This error may also indicate
that the docker daemon is not running.
Yes, the daemon is running, or at least it is shown as running under Services. I use it only with a local container and do not do anything remote.
Any suggestions on how this can be solved?
Well, I have had the same issue today and the only way for me to fix it was by reinstalling Docker (uninstall and install latest stable version)...
Now docker info runs OK and my solution builds again.
I hope it helps,
Juan
Note: it shouldn't have happened at all, I've lost at least one hour trying to figure out what and why it crashed...
Is Hyper-V running? You will get this error if Hyper-V closes down. Docker for Windows will still be "running", but the daemon will not work.

Resources