Error response from daemon dial unix docker raw sock connect no such file or directory

Error response from daemon: open /var/lib/docker/overlay2/XXX: no such file or directory #478

Expected behavior

docker push should push the given image to dockerhub.
docker save -o .tar should save the image to a tarball.

Actual behavior

docker push doesn’t push the image to dockerhub. I get an error saying

same error for docker save

Steps to reproduce the behavior

Try to build a caffe2 image. I double dog dare you.

Output of docker version :

Output of docker info :

Additional environment details (AWS, VirtualBox, physical, etc.)

The text was updated successfully, but these errors were encountered:

@huawei-tomas I have tried to reproduce this error with docker-ce version «18.06.1-ce» but I am unable to reproduce it. Can you please provide more details about the steps you have performed.

Its may be the issue with docker update in your system, you might have lost some file while installing or updating docker. Did try to uninstall docker and install it again?

I can reproduce the error.

I have to remove docker installation and clean /var/lib/docker folder.
Reboot and install docker again.
Enable docker (i.e. systemctl) and reboot again.

Event it is same in

did the trick for me, hope it helps

Has anyone solved this yet? I can’t push image to Docker Hub and got error.

After I prune system I re-downloaded older/same image but it failed.

That is strange.

did the trick for me, hope it helps

Didn’t work even after restart and reboot.

docker system prune -af worked for me

I fell into this problem because i tried to mv /var/lib/docker/overlay2 to some other place with docker starting. And docker system prune -af works for me.

docker system prune -af worked for me, thanks!

@fboulay you made my day , thanks!!

docker system prune -af worked for me, thanks

docker system prune -af

this command worked for me，thanks.

docker system prune -af worked, thanks !!

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

M1 preview: Docker always starting – dial unix docker.raw.sock: connect: no such file or directory #5253

Expected behavior

I get Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory trying to run docker by command line, and Dockers runnnig by the IDE.
Version: 20.10.1

Information

• macOS Version: Mac OSBigSur 11.0.1

Report issue> 6B14D24D-D134-4059-B90B-96E86A642DC5/20210114193921

The text was updated successfully, but these errors were encountered:

Same issue for me too. However, Docker was working perfectly fine (Mac M1 OS 11.1) until MacOS itself force-restarted the laptop due to an unknown fatal error. Since then, Docker has not worked.

1. Install AppCleaner
2. Open the Finder and go to Applications
3. Delete the Docker application
4. Click «Confirm» in the popup that AppCleaner shows, to delete all «related» files that Docker installed
5. Re-install Docker for M1 from https://docs.docker.com/docker-for-mac/apple-m1/
6. Repeat when you have to reboot
7. 😕

I use method from this link: https://forums.docker.com/t/restart-docker-from-command-line/9420
stop & start docker manually, and, it’s work.

How to control Docker for Mac from the CLI
Stop Docker for Mac gracefully

Note: Requires all Docker containers in the stopped state

Stop all Docker containers without confirmation (dangerous if running something)

Note: Assumes all running Docker containers are in a quiesced state

Start Docker gracefully

Note: It may take up to a minute for Docker to fully start

1. Install AppCleaner
2. Open the Finder and go to Applications
3. Delete the Docker application
4. Click «Confirm» in the popup that AppCleaner shows, to delete all «related» files that Docker installed
5. Re-install Docker for M1 from https://docs.docker.com/docker-for-mac/apple-m1/
6. Repeat when you have to reboot
7. 😕

not work for me, anyone succeeds?

@fiefdx ‘s solution worked for me

For me both solutions didn’t work

Report issue : 9CB11941-A621-44D4-8E9F-78E3E9F8BA1F/25640218072511

I faced the same issue, but I solved it below method.

1. Uninstall the docker preview app in the troubleshoot page on the dashboard
2. Re-install it
3. Open it
4. Type password correctly
5. Login docker account

I think this issue may cause due to password typo or something related to docker account.

How to control Docker for Mac from the CLI
Stop Docker for Mac gracefully

Note: Requires all Docker containers in the stopped state

Stop all Docker containers without confirmation (dangerous if running something)

Note: Assumes all running Docker containers are in a quiesced state

Start Docker gracefully

Note: It may take up to a minute for Docker to fully start

Источник

Docker daemon error /sys/fs/cgroup/cpuset/docker/cpuset.cpus: no such file or directory #33594

Description

Whenever I attempt to run a container, Docker throws the following oci runtime error:
applying cgroup configuration for process caused «open /sys/fs/cgroup/cpuset/docker/cpuset.cpus: no such file or directory»

When I examine the folder with ls /sys/fs/cgroup/cpuset/docker , I do indeed find that there is no cpuset.cpus file in that directory and for some reason I am not able to create one either.

I attempted to fix this problem by following the instructions in this comment, but it was unable to resolve the error.

It should be noted that I am running the docker daemon using sudo dockerd on ubuntu inside ChromeOS using the crouton package.

Full Error:

Output of docker version :

Output of docker info :

Output of docker-runc —version :

Output of mount :

Output of uname -a :

The text was updated successfully, but these errors were encountered:

I have exactly the same problem, also on Ubuntu inside ChromeOS.

it’s still around, seems peculiar to ChromeOS.
There exists a /sys/fs/cgroup/cpuset/docker/cpuset
so the missing cpuset.cpus shouldn’t be so alien to the kernel.
I tried manually touching a cpuset.cpus, and got Permission denied
so I reckon there’s something about cgroup privileges that restricts docker.

I also ran into the permission denied issue.

However, since installing GalliumOS on a second partition, I have not run into any problems running docker. Although Chromebooks require that linux distros be built from the ChromeOS kernal, unlike crouton, Gallium operates in its own environment. As a result, it is likely that this problem is tied to how Crouton handles mounting virtual devices which in turn relies upon how ChromeOS handles mounting. So, it is unlikely that this bug can be solved without compiling a new kernel based off of ChromeOS. which essentially would operate like Gallium.
https://arnoldthebat.co.uk/wordpress/chromiumos-special-builds/

So, even though this is still an open problem, I’m going to close it and recommend using GalliumOS.

Источник

Error response from daemon: Cannot start container: [8] System error: no such file or directory #14931

I just installed experimental docker and I get this error while trying to run hello world:

docker run hello-world

The text was updated successfully, but these errors were encountered:

Please read this important information about creating issues.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

This is an automated, informational response.

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version :
docker info :
uname -a :

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

Any chance you installed from the debian packages?

Not sure, I am in a Ubuntu 14.04 and did:

wget -qO- https://experimental.docker.com/ | sh

@bezelga you’re likely running into a bug with the apparmor profiles fixed in #14934. You can confirm by seeing if you have DENIED entries in your audit log (dmesg or, if you have auditd installed, in /var/log/audit/audit.log)

@bezelga If (and only if) you see those DENIED messages (especially if for auplink), then try checking out my PR and loading my apparmor policy:

If this works you can copy the contrib/apparmor/docker-engine file into /etc/apparmor.d. If not, then you could try loading it in «complain» mode by running ‘apparmor_parser -r -C’. That will generate logs for debugging.

I’m having the same result here.

The console log when I tried to run a new container:

The docker daemon log:

Seems like it got broken very recently, because it’s been working fine when I tried to install the experimental version just a day ago.

The below is the working experimental version(Git commit: 8c7cd78) i installed a few days ago. (It still works fine)

I hope this helps the investigation on what broke it.

And also, is there any way to install a previous version of the experimental docker? If so, please let me know. 🙂

looking into /var/log/dmesg I did not find any DENIED message.

these are the lines that contain apparmor stuff:

Let me know if there is anything else I can help.

In the meantime would be good to install that previous version @stewartpark mentioned.

@stewartpark hello there, did you figure out how to install that working version? thanks

+1
I am having the same problem. Installed using wget -qO- https://experimental.docker.com/ | sh on a fresh ubuntu 14.04 VM and I get the error. I am running the same version ( Git commit: e5d8fb9 ) as @stewartpark

@ewindisch I don’t have the /var/log/audit/audit.log file on my system and I don’t see any denied message in /var/log/dmesg

+1, exact same situation/outcome as @ankushagarwal

I’m also getting the same error with Docker 1.8.0-rc1

It worked for me in this experimental version:

For me it’s happening on 1.7.1

I’ve got an image which is hosted on the registry hub. On 4 out of 5 CoreOS machines, it can be pulled and run correctly. On the 5th machine, there is the same error as reported here when running the image. The machines are set up identically (CoreOS stable 717.3.0).

As this is an automated build, I tried rebuilding it. The new image has the same problem, but again, only on this one specific machine.

In the image folder in /var/lib/docker/overlay/5c01709e62f2a1d95560ff7b046e86b54ed1a57011bacbd52043d2dcd6c75ca0/root/ on the misbehaving server, I can see the following contents:

The same image on the other servers has a complete filesystem. The existence of the (empty) folder temp-docker-extract009171261 tells me there must have been some error during the pull. Which is confusing since there was no error message in the logs. Even with debug logging enabled, there is nothing particularly striking to see. Apart from the (debug-level) message Verification failed for xxx using key yyy..

Got this working using a workaround now. As we are using a private registry, too (using the —insecure-registry switch btw), I tried pushing the intact image from one of the other servers up there. Pulling that image from the misbehaving server yields a sane, runnable image again. Not sure what to make out this.

UPDATE: This workaround works only for one of the two image tags. Pushing the other one to the local registry yields the same erraneous result when pulled and run on that server.

Источник

starting container process caused: «exec: »/bin/sh»: stat /bin/sh: no such file or directory» #31702

Description
I have error after running RUN apt -yqq install nginx iputils-ping :

container_linux.go:247: starting container process caused: «exec: »/bin/sh»: stat /bin/sh: no such file or directory»
ERROR: Service ‘nginx’ failed to build: oci runtime error:

But the weird thing is, that when I had Docker installed previously, it never happend (I had Docker, uninstalled it and after some time installed again).

Steps to reproduce the issue:

1. Run docker-compose build
2. See error

Dockerfile

docker-compose.yml

Describe the results you received:

Describe the results you expected:
Build containers successfuly.

Output of docker version :

Output of docker info :

The text was updated successfully, but these errors were encountered:

You load the image when docker starting up. Just remove and install docker again. Work for me

I did it multiple times.

Tried to reproduce this and couldn’t. Our docker version is slightly different though:

I just encountered a similar problem on mac. docker/for-mac#1396 helped. I also did full docker cleanup first (removed unused images etc.)

Same problem here with Git commit 3a232c8.

I built my own image by writing an dockerfile.

Then I ran the command
sudo docker build -t persus/alpine-emby:3.2 -f emby.alpine.build.dockerfile .

When trying to run the newly built image by typing
sudo docker run -d —name emby -p 1900:1900/udp -p 8096:8096/tcp -p 7359:7359/udp -p 8920:8920/tcp persus/alpine-emby:3.2

I get a similar error message
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused «exec: »/sbin/start_runit»: stat /sbin/start_runit: no such file or directory».

I am new to docker. Am I doing something wrong?

Источник

Research

Before marked as dupe, I have done my research. I’ve tried the suggestion as well to add $USER to docker group, and log out, log in, even restart, execute newgrp docker all that is done
here

I just did what is written here in the docs to install Docker Desktop via the deb package, including the pre-requsite set-up repository here, plus the post-install step which mentioned adding user to docker group. Note I didn’t install the Docker Engine, because I thought its not necessary for Docker Desktop, this is correct right?

It seems like I have entirely different problem

Result

After installation I just simply run this systemctl --user start docker-desktop which opens up the DD (Docker Desktop) and it just says «docker desktop starting .. «

Here’s some maybe related result throughout my research:

1. sudo docker run hello-world

docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.

1. docker run hello-world

docker: Cannot connect to the Docker daemon at unix:///home/name/.docker/desktop/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

1. ls -la /var/run/docker.sock

srw-rw---- 1 root docker 0  9月 26 22:53 /var/run/docker.sock

1. docker version

Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory
Client: Docker Engine - Community
 Cloud integration: v1.0.29
 Version:           20.10.18
 API version:       1.41
 Go version:        go1.18.6
 Git commit:        b40c2f6
 Built:             Thu Sep  8 23:11:43 2022
 OS/Arch:           linux/amd64
 Context:           desktop-linux
 Experimental:      true

1. service docker status or sudo systemctl restart docker

Unit docker.service could not be found.

Number 5 is really weird, something I don’t find in other posts. How to fix the «Unit docker.service could not be found.» error?, here just mention about installing from snap, but not my case.

Any help is greatly appreciated, I’ve been stuck for ~6 hours try debugging this 🙏