Heard about the latest password breach (since lunch)? HaveYouBeenPowned yet (today)? Passwords are broken, and as the amount of sites for which you need to store credentials grows exponetially, so does the risk of using a common password.
"Duh, use a password manager", you say. Sure, but be aware that even password managers have security flaws.
OK, look smartass.. no software is perfect, and there will always be a risk of your credentials being exposed in ways you didn't intend. You can at least minimize the impact of such exposure by using a password manager to store unique credentials per-site. While 1Password is king of the commercial password manager, BitWarden is king of the open-source, self-hosted password manager.
Bitwarden is a free and open source password management solution for individuals, teams, and business organizations. While Bitwarden does offer a paid / hosted version, the free version comes with the following (better than any other free password manager!):
- Access & install all Bitwarden apps
- Sync all of your devices, no limits!
- Store unlimited items in your vault
- Logins, secure notes, credit cards, & identities
- Two-step authentication (2FA)
- Secure password generator
- Self-host on your own server (optional)
Setup data locations¶
We'll need to create a directory to bind-mount into our container, so create
/var/data/config/bitwarden/bitwarden.env, and leave it empty for now.
What, why an empty env file? Well, the container supports lots of customizations via environment variables, for things like toggling self-registration, 2FA, etc. These are too complex to go into for this recipe, but readers are recommended to review the dani-garcia/bitwarden_rs wiki, and customize their installation to suite.
Setup Docker Swarm¶
Create a docker swarm config file in docker-compose syntax (v3), something like this:
I share (with my patreon patrons) a private "premix" git repository, which includes necessary docker-compose and env files for all published recipes. This means that patrons can launch any recipe with just a
git pull and a
docker stack deploy 👍
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
version: "3" services: bitwarden: image: mprasil/bitwarden env_file: /var/data/config/bitwarden/bitwarden.env volumes: - /etc/localtime:/etc/localtime:ro - /var/data/bitwarden:/data/:rw deploy: labels: - traefik.enable=true - traefik.web.frontend.rule=Host:bitwarden.example.com - traefik.web.port=80 - traefik.hub.frontend.rule=Host:bitwarden.example.com;Path:/notifications/hub - traefik.hub.port=3012 - traefik.docker.network=traefik_public networks: - traefik_public networks: traefik_public: external: true
Note the clever use of two Traefik frontends to expose the notifications hub on port 3012. Thanks @gkoerk!
Launch Bitwarden stack¶
Launch the Bitwarden stack by running
docker stack deploy bitwarden -c <path -to-docker-compose.yml>
Browse to your new instance at https://YOUR-FQDN, and create a new user account and master password (Just click the Create Account button without filling in your email address or master password)
Get the apps / extensions¶
Once you've created your account, jump over to https://bitwarden.com/#download and download the apps for your mobile and browser, and start adding your logins!
Chef's Notes 📓¶
- You'll notice we're not using the official container images (all 6 of them required!), but rather a more lightweight version ideal for self-hosting. All of the elements are contained within a single container, and SQLite is used for the database backend.
- As mentioned above, readers should refer to the dani-garcia/bitwarden_rs wiki for details on customizing the behaviour of Bitwarden.
- The inclusion of Bitwarden was due to the efforts of @gkoerk in our Discord server- Thanks Gerry!
Tip your waiter (support me) 👏¶
Did you receive excellent service? Want to make your waiter happy? (..and support development of current and future recipes!) See the support page for (free or paid) ways to say thank you! 👏
Flirt with waiter (subscribe) 💌¶
Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated. (double-opt-in, no monkey business, no spam either - check the archive for proof!)