Squazz Posted February 10, 2019 Share Posted February 10, 2019 (edited) 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 February 10, 2019 by Squazz Quote Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 (edited) 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 February 10, 2019 by CHBMB Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 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 Quote Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 (edited) Well, you're using a release candidate, so probably should report it there. What version did you update from? Edited February 10, 2019 by CHBMB Quote Link to comment
JorgeB Posted February 10, 2019 Share Posted February 10, 2019 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. Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 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 Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 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? Quote Link to comment
JorgeB Posted February 10, 2019 Share Posted February 10, 2019 1 minute ago, Squazz said: How would I go around doing this? https://forums.unraid.net/topic/57181-real-docker-faq/?do=findComment&comment=564309 1 Quote Link to comment
bonienl Posted February 10, 2019 Share Posted February 10, 2019 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. 1 Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 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? Quote Link to comment
CHBMB Posted February 10, 2019 Share Posted February 10, 2019 I'm not sure how to use the restore function. Where should I look?The apps tab. And there will be something there to reinstall existing applications or something along those lines.Sent from my Mi A1 using Tapatalk Quote Link to comment
Squid Posted February 10, 2019 Share Posted February 10, 2019 2 minutes ago, CHBMB said: The apps tab. And there will be something there to reinstall existing applications or something along those lines. Sent from my Mi A1 using Tapatalk Previous Apps 1 Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 3 minutes ago, CHBMB said: The apps tab. And there will be something there to reinstall existing applications or something along those lines. Sent from my Mi A1 using Tapatalk Am I looking in the wrong place? Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 1 minute ago, Squid said: Previous Apps Ok, that's what I thought I had just hoped there was a "restore" button Quote Link to comment
Squazz Posted February 10, 2019 Author Share Posted February 10, 2019 Thank you so much everyone, I got everything up and running again Quote Link to comment
Stefan_H Posted May 26, 2023 Share Posted May 26, 2023 I also just got this Error because my System ran out of memory and from the logs i could tell that it killed the process with the highest memory consumption (dockerd). What worked for me was just running /etc/rc.d/rc.docker start in the Terminal to start it up again. Will of course not work if the docker image is really corrupt, but might be worth a try in cases similar to mine. 2 Quote Link to comment
roseatoni Posted August 18, 2023 Share Posted August 18, 2023 On 5/26/2023 at 6:43 AM, Stefan_H said: I also just got this Error because my System ran out of memory and from the logs i could tell that it killed the process with the highest memory consumption (dockerd). What worked for me was just running /etc/rc.d/rc.docker start in the Terminal to start it up again. Will of course not work if the docker image is really corrupt, but might be worth a try in cases similar to mine. Thank you! This worked for me. Quote Link to comment
Recommended Posts
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.