Updating is straightforward, you just make sure to preserve the mounted volume. If you used the bind-mounted path as in the example here, you just need to pull the latest image, stop and rm the current container and then start a new one the same way as before:
# Pull the latest version
docker pull vaultwarden/server:latest
# Stop and remove the old container
docker stop vaultwarden
docker rm vaultwarden
# Start new container with the data mounted
docker run -d --name vaultwarden -v /vw-data/:/data/ -p 80:80 vaultwarden/server:latest
Then visit http://localhost:80
In case you didn't bind mount the volume for persistent data, you need an intermediate step where you preserve the data with an intermediate container:
# Pull the latest version
docker pull vaultwarden/server:latest
# Create intermediate container to preserve data
docker run --volumes-from vaultwarden --name vaultwarden_data busybox true
# Stop and remove the old container
docker stop vaultwarden
docker rm vaultwarden
# Start new container with the data mounted
docker run -d --volumes-from vaultwarden_data --name vaultwarden -p 80:80 vaultwarden/server:latest
# Optionally remove the intermediate container
docker rm vaultwarden_data
# Alternatively you can keep data container around for future updates in which case you can skip last step.
You can also use a tool like Watchtower to automate the update process. Watchtower can periodically check for an update to the Docker image, pull the updated image, and recreate the container using the updated image.
Updating when using docker-compose
docker-compose down
docker-compose pull
docker-compose up -d
Updating when using systemd service (in this case Debian/Raspbian)
sudo systemctl restart vaultwarden.service
sudo docker system prune -f
#WARNING this could delete stopped or unused containers, etc. not associated with vaultwarden
#be carefull and look which containers you need
docker ps -a
#shows stopped containers
#WARNING! This will remove:
# - all stopped #containers
# - all networks not used by at least one container
# - all dangling images
# - all dangling build cache
#you can list docker images with
docker images
#there you see all unused images
#
The restart command will stop the container, pull the newest images, run the container again. The prune command will remove the now old container (-f stands for: Do not ask for confirmation).
Put these into cronjob if you want (time can be changed):
$ sudo crontab -e
0 2 * * * sudo systemctl restart vaultwarden.service
0 3 * * * sudo /usr/bin/docker system prune -f
Use the command
which docker
if /usr/bin/docker is not the correct path to docker
Updating when using DietPi
DietPi is a lightweight Debian-based distribution (image) for all kinds of devices like Raspberry Pi, Odroid, NanoPi and others. It offers a software script for installing various programs including Vaultwarden. That spares the user tinkering with installation commands.
Vaultwarden updates must be manually initiated by the user on DietPi, there is no automatic installation nor will apt update && apt upgrade perform an update. To update a previously installed Vautwarden instance which was installed using DietPi's software installation script, enter the following command on the DietPi's command line:
dietpi-software reinstall 183
It is recommended to use DietPi version 8.7 or newer because the update process has been considerably sped up compared to previous versions.
In case you have customised Vaultwarden's configuration file, it will be kept by the update script.
FAQs
Container Image Usage
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
Deployment
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
HTTPS
Configuration
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration
Database
- Using the MariaDB (MySQL) Backend
- Using the PostgreSQL Backend
- Running without WAL enabled
- Migrating from MariaDB (MySQL) to SQLite