Docker install update about cmc-csci143 HOT 12 CLOSED

Mine wasn't working until I edited my unit file at ~/.config/systemd/user/docker.service. This is for those who get status=203/EXEC error (I'm assuming this applies to most people with daemon connection error). To fix it, change the directory of ExecStart to ExecStart=/home/username/.local/bin/dockerd-rootless.sh (replace username with yours).

Hope this helps!

from cmc-csci143.

Samuel's fix worked for me! Thank you so much!

from cmc-csci143.

I previously "fixed" the problem by rerunning the install procedure. However I noticed that the fix worked because the $HOME/bin folder was reinstalled. Samuel's fix addresses the removal of the $HOME/bin folder.

from cmc-csci143.

@amytam01 It's a rather hard to read your post since all your commands are intermixed with normal text... but it looks like you are running the command

DOCKER_HOST=unix:///run/user/1001/docker.sock

when you should be using the export command to set the DOCKER_HOST, something like

export DOCKER_HOST=unix:///run/user/1001/docker.sock

Also, the string that you have to the right of the = is rather suspicious... the number 1001 is almost certainly supposed to be your user id, and your userid is not 1001.
If you run the command

export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/docker.sock

it should set the variable correctly.

from cmc-csci143.

@amytam01 I'll probably need to look at this over zoom with you to keep making progress. But the "nuclear" option is to delete everything in your home folder. And use ls -a to make sure you delete everything, including hidden files. Then you should be able to install from scratch without your previous installations getting in each other's way.

from cmc-csci143.

Worked for me; thank you!

from cmc-csci143.

I've done everything suggested here. I "fixed" Docker after rerunning the install procedure and it worked until it didn't 15 minutes later. I have almost no idea why it broke.

Then, I tried to fix it by rerunning the install procedure and when that didn't work I attempted Samuel's fix and checked that everything from bin was moved to .local/bin and put the command DOCKER_HOST=unix:///run/user/1001/docker.sock in my .bashrc file. After running systemctl --user start docker I have no errors pop up, but when I try docker run ubuntu I get this classic error message: "docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create: dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'.". I've tried exiting, restarting multiple times and everything.

Please help :')

from cmc-csci143.

So I've ironed out some of the initial problems as mentioned by @mikeizbicki and ended up redoing the entire process and now have the correct export command in my .bashrc file. I've also made sure (again and again) that my docker files are not in bin but .local/bin. I've also followed Sam's suggestions and made sure my unit file was correct in ~/.config/systemd/user/docker.service

Now when I run
systemctl --user start docker
I have no problems, but when I try to run
docker run ubuntu
I get the following error:
-bash: /home/atam/bin/docker: No such file or directory
I think I got this error after moving my files from bin to .local/bin and I've reinstalled Docker at least 5 times (so maybe that's the problem?) I always assumed that my files were being rewritten each time they were moved. Thanks!

Edit: I've learned so much about docker commands and process after all of these issues, but I still can't get it to work xD

from cmc-csci143.

@amytam01 Have you also updated your PATH? The command is

$ export PATH=~/.local/bin:$PATH

The fact that your error message begins with bash: means that it is bash that is trying to find the executable, and it cannot. And this suggests a malformed PATH.

from cmc-csci143.

@amytam01 Have you also updated your PATH? The command is

$ export PATH=~/.local/bin:$PATH

The fact that your error message begins with bash: means that it is bash that is trying to find the executable, and it cannot. And this suggests a malformed PATH.

So I did as you suggested, and realized that I didn't update this copied and pasted version of my problem. My current issue is that I'm getting is docker: Cannot connect to the Docker daemon at unix:///run/user/1137/docker.sock. Is the docker daemon running?.

from cmc-csci143.

@mikeizbicki I just ran into a similar issue as @amytam01 for some unknown reason, but trying the nuclear option didn't help at all. Need help!!!

from cmc-csci143.

@hfaara18 Without showing me what commands you are running and the corresponding error messages, there's no way for me to help.

from cmc-csci143.