Some docker containers will not start after swapping cache SSD

[Statia]

I set any shares using cache to Cache:YES and used mover and a combination of UnBalance to move my cached files to the array. Swapped out my cache SSD and set the cache:<setting> back on each share before using UnBalance to move the files back to the SSD as required.

 

Since then, some of my dockers will not run with the error:

 

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/init": stat /init: no such file or directory: unknown.

 

I have reinstalled some and that has fixed them, but others still will not fire up.

 

Diagnostics attached, please can someone assist?

 

 

nas-diagnostics-20221120-1804.zip

Edited November 20, 2022 by Statia

[Squid]

Nov 20 17:59:33 nas CA Backup/Restore: Backup / Restore Completed

 

Why not instead restore the backup you had previously made before the SSD swap?

1. It always works
2. Probably about 100x faster than using UnBalance to move stuff around and at least 1000x faster than doing the same thing with mover?

 

Having you tried recreating the docker image yet?

[Statia]

Quote

Why not instead restore the backup you had previously made before the SSD swap?

I did try this but had the same outcome. I also tried restoring from Nov 19 too but it was still broken. I am currently deleting my docker folder and will see if that fixes it.

[Statia]

I removed the docker folder and added back the containers once that was completed from Apps > Previous Apps and it's all working again.