Error while restarting Bitwarden

Ask the Community Password Manager
1

sudo ./bitwarden.sh restart
httpsgithubcom/bitwarden===================================================Docker version 18.09.7, build 2d0083ddocker-compose version 1.24.0, build 0aa59064
Removing network docker_default
WARNING: Network docker_default not found.
Pulling mssql … error
Pulling web … error
Pulling attachments … error
Pulling api … error
Pulling identity … error
Pulling admin … error
Pulling icons … error
Pulling notifications … error
Pulling nginx … error
ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io: no such host

what could be the Problem ?

2

Looks like a network or dns issue on your machine. The script couldn’t connect to the docker hub and docker registry.

3

New error

Docker version 18.09.7, build 2d0083d
docker-compose version 1.24.0, build 0aa59064

Stopping bitwarden-nginx … error
Stopping bitwarden-admin … error
Stopping bitwarden-icons … error
Stopping bitwarden-api … error
Stopping bitwarden-identity … error
Stopping bitwarden-attachments … error
Stopping bitwarden-notifications … error
Stopping bitwarden-mssql … error
Stopping bitwarden-web … error

ERROR: for bitwarden-notifications cannot stop container: a44a6fdfbe6e4cc1aba3f7438a6ad663a74e574199d6a9c153bdceb0e87755a2: Cannot kill container a44a6fdfbe6e4cc1aba3f7438a6ad663a74e574199d6a9c153bdceb0e87755a2: unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused “permission denied”
: unknown

ERROR: for bitwarden-nginx cannot stop container: 593cd7c82cf616e6a5134695829accc8ca66ab55a04371d22f034607d7fe2ae7: Cannot kill container 593cd7c82cf616e6a5134695829accc8ca66ab55a04371d22f034607d7fe2ae7: unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused “permission denied”
: unknown

ERROR: for bitwarden-attachments cannot stop container: 91513c3ac2668a89322e0ec8661d75510f826e36616ce9822af8fb73b119f9d6: Cannot kill container 91513c3ac2668a89322e0ec8661d75510f826e36616ce9822af8fb73b119f9d6: unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused “permission denied”
: unknown

ERROR: for bitwarden-icons cannot stop container: 914ba01d6dd64f00e396222d3a4c4addeccaf2151074d6960f3338dae5e66972: Cannot kill container 914ba01d6dd64f00e396222d3a4c4addeccaf2151074d6960f3338dae5e66972: unknown error after kill: runc did not terminate sucessfully: container_linux.go:388: signaling init process caused “permission denied”

4

Are you root or using sudo?

5

Im trying to restart it as sudo

6

And i tried it as root too

7

Thread, rise from your grave!
Just in case someone else tries searching the forum for this error - in my case it turned out to be a DNS issue. Cloudflare DNS and the local DNS servers were all getting inconsistent results when trying to resolve the docker.io address, for some reason. Switching the local Bitwarden host to use Google DNS (8.8.8.8, 8.8.4.4) fixed it for me.