[SOLVED] bitwarden docker image Topic is solved

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
norrin
Posts: 10
Joined: Wed Oct 24, 2018 9:42 am

[SOLVED] bitwarden docker image

Post by norrin »

Hi.
It is the first time that i use docker, so maybe there is the problem.

I installed docker and the bitwarden_rs docker image:
https://hub.docker.com/r/mprasil/bitwarden/#features

It is an Bitwarden server API implementation written in Rust compatible with upstream Bitwarden clients, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal.
So it should run on raspberries and odroids.

Just install docker by the dietpi-software-tool and enter

Code: Select all

sudo docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 mprasil/bitwarden:raspberry
Everything else will be installed automatically.
Then you can login at http://<<dietpi-ip>>:80 and start your password-manager.
odroid XU4
huidbui25
Posts: 32
Joined: Tue May 07, 2019 7:07 pm
Location: DE

Re: [SOLVED] bitwarden docker image

Post by huidbui25 »

Update: you should use bitwardenrs/server instead of this mprasil image as that is the new official image. Explanation below shows how to.

So, after having installed docker through dietpi-software perform the following commands (adapted for Raspberry Pi):

Code: Select all

docker pull bitwardenrs/server:raspberry
docker run -d --name bitwarden -v /bw-data/:/data/ -p 80:80 bitwardenrs/server:raspberry
Hints:
  • Do not change the containerPort argument, that's the part after the colon. Leave it to :80 as otherwise you cannot establish a connection to the Bitwarden WebVault in the docker image.
  • However, you may change the hostPort, i.e. the part in front of the colon, to any (free) port you like, e.g. 4567. You might have to do this when you have a web server running and listening on port 80 already on your system. Docker would throw an error message then.
  • You may also like to assign a fixed hostIP in case this suits your setup. This way docker will bind the hostPort (e.g. 4567) to that particular IP (e.g. 192.168.0.2) and hence prevent the port from being exposed to the whole world.
Taking this into consideration, the docker run command could look like this:

Code: Select all

docker run -d --name bitwarden -v /bw-data/:/data/ -p 192.168.0.2:4567:80 bitwardenrs/server:raspberry
Further information can be found here:
https://github.com/dani-garcia/bitwarden_rs
Post Reply