Mobutils

It appears that my Unraid server updated a bunch of my binhex docker containers, and a a number of them are now no longer starting. When trying to start the docker instance from the Unraid interface I am presented with a `Execution Error: Bad Parameter` which wasn't very clear so I went to see if starting these docker instances from the cli would give ore information: root@Tardis:~# docker start binhex-plexpass Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown Error: failed to start containers: binhex-plexpass This is also occurring for `binhex/nzbget` `binhex-nzbhydra` `binhex-overseerr` `binhex-radarr` all of these were reported being updated about 2 day ago. root@Tardis:~# docker start binhex-nzbget Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown Error: failed to start containers: binhex-nzbget root@Tardis:~# docker start binhex-nzbhydra2 Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown Error: failed to start containers: binhex-nzbhydra2 root@Tardis:~# docker start binhex-overseerr Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown Error: failed to start containers: binhex-overseerr root@Tardis:~# docker start binhex-radarr Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown Error: failed to start containers: binhex-radarr Any suggestions on what might be done to resolve this? Much appreciated! --- Edit: More info, Removing the container, and reinstalling results in the same error: docker run -d --name='binhex-overseerr' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tardis" -e HOST_CONTAINERNAME="binhex-overseerr" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5055]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/overseerr-icon.png' -p '5055:5055/tcp' -v '/mnt/disks/HP_LOGICAL_VOLUME/appdata/binhex-overseerr':'/config':'rw' 'binhex/arch-overseerr' e401b19849afefd1122b9446a707f54f8f87018af4a5c0dac46b21b81a1dff33 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": stat /usr/bin/dumb-init: no such file or directory: unknown. The command failed. Edit #2: Issue Resolved Removed all offending containers and associated images and reinstalled. Ran a `docker [container/image/volume/system] prune`. I assume one of the supporting images was corrupted somehow and the image was cached and not reinstalled during the previous attempt.