[GH-ISSUE #435] Admin Panel #260

New issue

Closed

opened 2026-03-03 01:27:20 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:27:20 +03:00

Owner

Originally created by @daxda on GitHub (Mar 16, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/435

Hi! I have a problem with the activation of the admin panel. when I try to give the command I found on the wiki. I get this error:

docker: Error response from daemon: Conflict. The container name "/bitwarden" is already in use by container "9c51e44c50f2bcaf80ebbb7c018caf923e89d2c5735e17f665d5ee6f6ff87da7". You have to remove (or rename) that container to be able to reuse that name.

Originally created by @daxda on GitHub (Mar 16, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/435 Hi! I have a problem with the activation of the admin panel. when I try to give the command I found on the wiki. I get this error: docker: Error response from daemon: Conflict. The container name "/bitwarden" is already in use by container "9c51e44c50f2bcaf80ebbb7c018caf923e89d2c5735e17f665d5ee6f6ff87da7". You have to remove (or rename) that container to be able to reuse that name.

kerem

2026-03-03 01:27:20 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:27:21 +03:00

Author

Owner

@mprasil commented on GitHub (Mar 16, 2019):

What docker command tells you back is your issue. You probably ran the container with the same name already - most likely from your previous docker run command? You can see all containers (including stopped ones) with docker ps -a.

You can remove stopped container with docker rm <container_name>.

I assume you're following the wiki. It doesn't say that explicitly, but you cannot change running container settings just by re-running docker run command with different parameters. You need to stop previous container, rm it if you want to keep the same name and start again with new parameters. Hope that helps.

@mprasil commented on GitHub (Mar 16, 2019): What docker command tells you back is your issue. You probably ran the container with the same name already - most likely from your previous `docker run` command? You can see all containers (including stopped ones) with `docker ps -a`. You can remove stopped container with `docker rm <container_name>`. I assume you're following the wiki. It doesn't say that explicitly, but you cannot change running container settings just by re-running `docker run` command with different parameters. You need to stop previous container, `rm` it if you want to keep the same name and start again with new parameters. Hope that helps.

kerem commented

2026-03-03 01:27:21 +03:00

Author

Owner

@mprasil commented on GitHub (Apr 10, 2019):

I'm going to close this as I think the question was answered, but feel free to reopen if you have more questions regarding this.

@mprasil commented on GitHub (Apr 10, 2019): I'm going to close this as I think the question was answered, but feel free to reopen if you have more questions regarding this.