Closed YStrauch closed 2 years ago
Okay I get this error with another docker container as well, seems not to be an issue with BitBetter. Will close this as it's not your problem to fix my docker :)
Okay just in case someone has the same problem - somehow my docker got corrupted and after a re-installation everything works again. Not an issue with BitBetter.
Hi!
Today BitWarden did not start, it tried pulling the api and identity containers (I probably forgot to disable the dockerComposePull in my last update).
So I ran update-bitwarden.sh. One persistent warning(?) during update that keeps popping up is:
failed to register layer: rename /var/lib/docker/image/overlay2/layerdb/tmp/write-set-939942720 /var/lib/docker/image/overlay2/layerdb/sha256/e2fb40b483c432be48e29a059ab8b143f3a6266a593619fd49b63a3b82d19f3d: file exists
But the update continues so I ignored it. I proceeded to uncomment dockerComposePull as per your guide and tried starting bitwarden. This now fails with
ERROR: layer does not exist
.So I guess that the layer thing above is something I should not ignore. I tried removing the file that "already exists" (the second path), I tried
docker image prune --all
and evendocker system prune --all
but it just won't start. My git repo is up-to-date.Sorry if this is a user error!