Portainer Templates logo

Portainer Templates

Bitwarden RS Bitwarden RS

Container

OtherTools

This is a 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..

Image details

Pulls: 328.0M
Architecture: amd64, arm64, arm/v7, arm/v6, arm, arm64/v8
Image size: 92 MB
Latest: 1.24.0-arm32v6
User: bitwardenrs
Created: May 12, 2019
Updated: 4 years ago
Status: archived

Configuration

Type
Container
Platform
linux
Image
bitwardenrs/server:latest
Ports
80/tcp
Volumes
/config : /portainer/Files/AppData/Config/Bitwarden-rs
Restart
unless-stopped

Template by mikestraney

Notes

This project is not associated with the Bitwarden project nor 8bit Solutions LLC.

Standalone Install

Select an install method, to see config/commands for deploying Bitwarden RS

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Bitwarden RS, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation.

⚠️ This image is deprecated ⚠️

BitwardenRS has been renamed to Vaultwarden, the new image is located here:

vaultwarden/server

This image contains support for all three database backends: SQLite, MySQL and PostgreSQL.
You can read more about the rename here: #1642

Serve Bitwarden RS on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying bitwarden-rs.example.com to http://bitwardenrs:80

Add this to your Caddyfile

bitwarden-rs.example.com {
	reverse_proxy http://bitwardenrs:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs bitwardenrs
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 80/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port bitwardenrs

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/Bitwarden-rs

Image won't pull

Test the pull directly on the host: docker pull bitwardenrs/server:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7, arm/v6, arm, arm64/v8
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect bitwardenrs --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Bitwarden RS runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Bitwarden RS needs bundled into one download. This template pulls bitwardenrs/server:latest, which Docker fetches once (about 92 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Bitwarden RS's comes from Docker Hub, published by bitwardenrs.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.24.0-arm32v6. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm/v6, arm, arm64/v8, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 80, published on a random host port

Volumes

A volume is where Bitwarden RS keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /config from /portainer/Files/AppData/Config/Bitwarden-rs on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Bitwarden RS after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Bitwarden RS sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container bitwardenrs. That's what you'll spot in the containers list and use in commands like docker logs bitwardenrs.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Bitwarden RS up. Add the template list to Portainer once, then deploying Bitwarden RS is a click rather than a wall of config.