Install Bitwarden Docker


Install Docker

Installing the Application via Docker. I’m going to be generally following directions here and here. First thing you need to do is SSH into your NAS. Change over to your docker location. Cd /volume1/docker. Install bitwarden with these commands. Sudo curl -Lso bitwarden.sh && chmod +x bitwarden.sh. Self-host Bitwarden on Synology NAS Instructions. Download and install Docker from the Synology Package Center. Before we get started, we need a directory where Bitwarden can add all of its files. Open “File Station”, navigate to the “docker” folder and create a subfolder named “bitwarden”. 5/3/21 Update: The bitwardenrs image. The base image used to serving static content such as the Bitwarden web vault. In this blog post I’ll be covering how to install a self hosted Bitwarden server as a password management solution using Docker on a Raspberry Pi. We will get two containers running (Bitwarden server) and (Nginx reverse proxy). I’ll also go into hardening the Bitwarden configuration and applying 2FA for log-ins.

Add user(s) to the docker group. The default user would be pi. However, I highly recommend deactivating the default user.

Reboot and then test docker

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Install more dependencies

Fight With SSL

This is the most annoying part of the story. You can either choose to use letsencrypt or a self-signed openssl-cert. Letsencrypt will only work, if your service will be exposed publicly. Also, letsencrypt is fairly easy to setup, so I will focus on a self-signed openssl-solution.

First, we’ll need a “virtual” certificate authority (CA) that will actually sign our certificate later. If you already have a CA, you can skip this. The first command creates a private key, the second command creates the root certificate of our CA.

Now, we’ll need to create a “client” key and a certificate signing request, which will then be “sent” to our CA.

For the actual signing, we’ll also need an extension file. I ran into problems with OSX and iOS without adding the used extensions during signing. Neither OSX, iOS nor Google Chrome accepted the certificate without those extensions. Create a file openssl.cnf

Replace <hostname> and <ip> with your actual values.

Finally, the actual signing:

The certificate you’ll need to deploy on your devices is the root certificate. Yes, this will also work on iOS.


Install/Configure Bitwarden


We’ll use the bitwarden_rs docker container. It uses sqlite instead of MSSQL, which is not available for ARM.

Setup bitwarden docker

Install Bitwarden Docker Synology

If docker successfully downloaded the image, you can run it as follows. I simply created a small bash script.

The ROCKET_TLS argument tells bitwarden, where it can find its key and certificate. The values describe paths within the docker container. For these paths to work, we’ll need to supply a volume mapping (-v). The additional volume mapping bw-data is a volume for bitwarden to store its actual sqlite “database” in. Internally, bitwarden will bind to port 80. Since we know/hope it’ll run SSL, we can map internal port 80 to 443.

Setup Bitwarden Docker

If everything works, you can reach your bitwarden vaults on https://<hostname>

You’ll most likely run into SSL problems. Good luck.


Install Bitwarden Without Docker

Read this article.


Show running docker containers

Logs and events

Run command within a docker container

Netstat (works w/o actual netstat binary in container. Cool, eh!?)

Install Bitwarden Without Docker

A word on IPv6. Initially, when bitwarden didn’t work during my first attempts, I was confused by the output of netstat. It showed, that the destination socket for https was only bound to tcp6. This shouldn’t be a problem, though, because bitwarden also sets up a couple of iptables rules (# iptables -L). However, if you think it might be a problem on your machine, try the following things in your /etc/sysctl.conf

Install Bitwarden Docker Compose

At one point, I even completely disabled IPv6 via the kernel command line. However, that introduced even more problems.

  • Most Viewed News

    • Macos Docker Container
    • Daisydisk Free Download
    • Macos 9 Iso