I recently had a disk failure that required me to move the location of Docker to another drive. I have my config files in a different "AppData" folder so at worst I have had to execute the docker compose files again. I am having some errors with a few of the containers. While trying to re-create Docker I copied over the existing Docker installation. I suspect that the "overlay2" folder had issues as I eventually had to exclude it from the copy as it was erroring out.
The errors seem to be somewhat similar. For example, Murmur is erroring out:
version: '3' services: murmur: image: goofball222/murmur container_name: Murmur ports: - 64738:64738 - 64738:64738/udp volumes: - /etc/localtime:/etc/localtime:ro - ./cert:/opt/murmur/cert - ./config:/opt/murmur/config - ./data:/opt/murmur/data - ./log:/opt/murmur/log environment: - TZ=America/New_York
resulted in this:
ERROR: for Murmur Cannot create container for service murmur: open /srv/dev-disk-by-label-Backup/Docker/overlay2/59aa666136ad027d5ef4de282616fa10fffe4d06a3d451f5267995dcdd3241c2/link: no such file or directory
ERROR: for murmur Cannot create container for service murmur: open /srv/dev-disk-by-label-Backup/Docker/overlay2/59aa666136ad027d5ef4de282616fa10fffe4d06a3d451f5267995dcdd3241c2/link: no such file or directory
ERROR: Encountered errors while bringing up the project.
Mariadb (which also worked fine before) had a similar issue:
Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/
ERROR: stat /srv/dev-disk-by-label-Backup/Docker/overlay2/36ae00f9c685ad098084c6107bab35d563fb2da27e626c60bd4a540acfd7c6c0: no such file or directory