Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Docker service failed to start - Invalid argument supplied for foreach()

Featured Replies

Just restarted my Docker service after a parity update and get this error. Please tell me I haven't lost all my dockers!

 

I had to cancel a CA Appdata backup during the parity check as it was slowing it down too much and get this error there:

 

Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (No such file or directory) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682
Couldn't create socket: [2] No such file or directory
Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 866

 

  • Author

I have tried deleting the docker.img but unfortunately most of my dockers no longer work after being restored - nextcloud, radarr, sonarr, rutorrent, calibre-web-automated

 

Is there any way at all of using the old docker.img? I think it must have been something to do with aborting the CA Appdata backup during the parity rebuild?

  • Author
5 minutes ago, JorgeB said:

Please post the diagnostics.
 

Here you go. Recreating all these dockers from scratch is going to take me a couple of days work at least which I really don't have so restoring the old docker.img would be preferable.

 

Is there any reason why the docker.img is never backed up?

fs-diagnostics-20250331-0940.zip

  • Author

I had all these errors in the CA_backup log: 

 

[31.03.2025 07:21:18] Verifying Backup 
[31.03.2025 07:25:39] User aborted backup!
[31.03.2025 07:25:39] done
[31.03.2025 07:25:39] Starting audiobookshelf... (try #1)  Error while starting container! - Code: 
[31.03.2025 07:25:44] Starting audiobookshelf... (try #2)  Error while starting container! - Code: 
[31.03.2025 07:25:49] Starting audiobookshelf... (try #3)  Error while starting container! - Code: 
[31.03.2025 07:25:49] Container did not started after multiple tries, skipping.
[31.03.2025 07:25:51] Starting calibre-web-automated... (try #1)  Error while starting container! - Code: 
[31.03.2025 07:25:56] Starting calibre-web-automated... (try #2)  Error while starting container! - Code: 
[31.03.2025 07:26:01] Starting calibre-web-automated... (try #3)  Error while starting container! - Code: 
[31.03.2025 07:26:01] Container did not started after multiple tries, skipping.

 

  • Community Expert
1 hour ago, cinereus said:

Recreating all these dockers from scratch is going to take me a couple of days work

It should be fairly quick if you use CA's previous apps:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

  • Author

That's exactly what I've done. But as I said, many dockers aren't working (and there doesn't seem to be a way to find out which dockers were actually currently installed).

 

Nextcloud isn't working at all after restoring for example.

 

Is there any indication from the logs why docker.img was corrupted?

  • Community Expert
57 minutes ago, cinereus said:

But as I said, many dockers aren't working

That suggests there's an issue with appdata, or they should all work.

 

57 minutes ago, cinereus said:

Is there any indication from the logs why docker.img was corrupted?

Not really, but there appears to have been a container constantly restarting, if it's still happening check the container uptimes.

  • Author
1 minute ago, JorgeB said:

That suggests there's an issue with appdata, or they should all work.

 

Not really, but there appears to have been a container constantly restarting, if it's still happening check the container uptimes.

I think it might be a docker network issue. All appdata backups have the same problem 

 

1. How can I backup docker network settings as well as appdata?

2. And why don't we backup docker.img too?

  • Community Expert
1 hour ago, cinereus said:

How can I backup docker network settings

AFAIK that cannot be backed up, you must recreate any custom network when the image is recreated, see link above.

 

 

 

 

  • Author
20 minutes ago, JorgeB said:

AFAIK that cannot be backed up, you must recreate any custom network when the image is recreated, see link above.

 

 

 

 

Is there any way to keep a record of images that are actually installed rather than have been installed at some time in the past?

 

Or to backup network settings?

  • Community Expert

Not that I know of.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.