Docker service wont start


Squazz

15 posts in this topic Last Reply

Recommended Posts

I get the following error message

Quote

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 654
Couldn't create socket: [111] Connection refused
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 826

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 654
Couldn't create socket: [111] Connection refused
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 890

Does anyone know what that means and what I should do about it?

 

Edited by Squazz
Link to post
5 minutes ago, Squazz said:

I get the following error message

Does anyone know what that means and what I should do about it?

 

Not without more context.  Need to see what you're doing to generate that error message.   To clarify, is it the docker service that won't start?  Or a docker container?  If it's the former, you need to post diagnostics, if it's the latter then some more info on the container etc

Edited by CHBMB
Link to post
5 hours ago, CHBMB said:

Not without more context.  Need to see what you're doing to generate that error message.   To clarify, is it the docker service that won't start?  Or a docker container?  If it's the former, you need to post diagnostics, if it's the latter then some more info on the container etc

My bad :) It went a little fast with that post ;)

It's the service that won't start

 

Diagnostics: nas-diagnostics-20190210-1626.zip

Image where I got the error-message

image.thumb.png.306a3c51b8601e4e4dffd13c8663275b.png

Link to post
6 minutes ago, CHBMB said:

Well, you're using a release candidate, so probably should report it there.

What version did you update from?

I upgraded to the release candidate because I had the problem before on version 6.6.6
Upgrading to the release candidate however gave me the error message, that I didn't have before

Link to post
3 minutes ago, johnnie.black said:

Feb 10 16:21:58 NAS kernel: BTRFS warning (device loop2): csum failed root 5 ino 15295 off 0 csum 0x98f94189 expected csum 0xd349d779 mirror 1

 

Docker image is corrupt, delete and recreate.

How would I go around doing this? :)

Link to post
2 minutes ago, Squazz said:

Upgrading to the release candidate however gave me the error message, that I didn't have before

In Unraid 6.7 we do not suppress PHP warnings anymore.

 

Please follow the advice of @johnnie.black and delete/recreate your docker image. You will need to re-install your containers, if you have CA installed, you can use its restore function to quickly get back all your containers.

Link to post
1 hour ago, bonienl said:

In Unraid 6.7 we do not suppress PHP warnings anymore.

 

Please follow the advice of @johnnie.black and delete/recreate your docker image. You will need to re-install your containers, if you have CA installed, you can use its restore function to quickly get back all your containers.

I'm not sure how to use the restore function. Where should I look?

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.