Hello,

I'm getting this error:

Quote

Warning: syntax error, unexpected end of file in /boot/config/docker.cfg on line 2 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 50

Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 50

 

and I can't access the dockers. They're still running though.

It's not the first time this happened. Last time I looked into it and couldn't quite figure out what it was about, so I decided to reboot the server, and it fixed it for a while, but now it's back.

 

What is it, and how do I fix it so it doesn't happen again?

Post your diagnostics when you're getting that error

1 hour ago, Squid said:

Post your diagnostics when you're getting that error

My bad, forgot it.

Here it is.

nanostorage-diagnostics-20220220-1445.zip

Corruption on that file (docker.cfg) at the very least

LOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE= 'mnT.user/system/docker/docker.img"
DOCKER_IMAGE_SIZE<b40"
DOCOER_APP_CONFIG_PA]H="/mnt/user/appdata/"
DOCKGR_QPP_UNRAA_PATH5""
DOCKER_CUSTOM_NETGORKS=" "
DOCJER_TIMEOUT}"10#
DOCKER_LOG_ROTAION="yes"
DOCKER_LOÇ_SIZE="µ0m"
ÄNCKER_LKG_FILES="1"
DOCKER_AUTHOBING_MMDE=#no"
DOCKER_USER_NETWORKS="remove"

 

Restore the flash drive from a backup.  Or if none available, delete the file from the flash and reboot (it looks to be basically stock anyways)

17 minutes ago, Squid said:

Corruption on that file (docker.cfg) at the very least

LOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE= 'mnT.user/system/docker/docker.img"
DOCKER_IMAGE_SIZE<b40"
DOCOER_APP_CONFIG_PA]H="/mnt/user/appdata/"
DOCKGR_QPP_UNRAA_PATH5""
DOCKER_CUSTOM_NETGORKS=" "
DOCJER_TIMEOUT}"10#
DOCKER_LOG_ROTAION="yes"
DOCKER_LOÇ_SIZE="µ0m"
ÄNCKER_LKG_FILES="1"
DOCKER_AUTHOBING_MMDE=#no"
DOCKER_USER_NETWORKS="remove"

 

Restore the flash drive from a backup.  Or if none available, delete the file from the flash and reboot (it looks to be basically stock anyways)

Alright.

How does this happen, and how did you figure it out from that?
Can I just browse to the file with SSH or Krusader and delete the file and reboot?

6 minutes ago, Nanobug said:

How does this happen, and how did you figure it out from that?

Missing quotes, mnT.user/system..... isn't a valid path etc  Easiest way for any flash to get corrupted is during a power cut in the middle of a write

 

6 minutes ago, Nanobug said:

Can I just browse to the file with SSH or Krusader and delete the file and reboot?

Or via SMB to the Flash share if it's exported (config folder)

 

If this is a continuing issue, then you'll need to ultimately replace the flash drive

38 minutes ago, Squid said:

Missing quotes, mnT.user/system..... isn't a valid path etc  Easiest way for any flash to get corrupted is during a power cut in the middle of a write

 

Or via SMB to the Flash share if it's exported (config folder)

 

If this is a continuing issue, then you'll need to ultimately replace the flash drive

I deleted the filed, rebooted Unraid, and enabled the docker image.
The error disappared for now (it worked with a reboot last time).
 

Is it happens again, I'll replace the USB stick.
Is there a way to test if the USB stick is bad?

Unraid does a quick check on the integrity of the flash on every reboot, and in 6.10+ it also does a quick check on certain files to make sure they're readable (the ones which are guaranteed to exist -> of which docker.cfg is one of them) and alerts you in the GUI if there's any problems

 

To really check, power down, pull the stick and run the file system checks on it in a Windows / Mac box

That would suck to do that

 

But If I need to do it, what sort of tool would you recommend?

I'd just Google and try the first one I find, but I have no experience in checking a USB stick.

Toss the drive in, right click on it from My Computer/This PC, Properties, Tools, Check