5

Changing persistent data location

Proxymiity ☆ edited this page 2021-04-29 20:43:39 +02:00

Table of Contents

• /data prefix:
• database name and location
• attachments location
• icons cache

/data prefix:

By default all persistent data is saved under /data, you can override this path by setting the DATA_FOLDER env variable:

docker run -d --name vaultwarden \
  -e DATA_FOLDER=/persistent \
  -v /vw-data/:/persistent/ \
  -p 80:80 \
  vaultwarden/server:latest

Notice, that you need to adapt your volume mount accordingly.

database name and location

Default is $DATA_FOLDER/db.sqlite3, you can change the path specifically for database using DATABASE_URL variable:

docker run -d --name vaultwarden \
  -e DATABASE_URL=/database/vaultwarden.sqlite3 \
  -v /vw-data/:/data/ \
  -v /vw-database/:/database/ \
  -p 80:80 \
  vaultwarden/server:latest

Note, that you need to remember to mount the volume for both database and other persistent data if they are different.

attachments location

Default is $DATA_FOLDER/attachments, you can change the path using ATTACHMENTS_FOLDER variable:

docker run -d --name vaultwarden \
  -e ATTACHMENTS_FOLDER=/attachments \
  -v /vw-data/:/data/ \
  -v /vw-attachments/:/attachments/ \
  -p 80:80 \
  vaultwarden/server:latest

Note, that you need to remember to mount the volume for both attachments and other persistent data if they are different.

icons cache

Default is $DATA_FOLDER/icon_cache, you can change the path using ICON_CACHE_FOLDER variable:

docker run -d --name vaultwarden \
  -e ICON_CACHE_FOLDER=/icon_cache \
  -v /vw-data/:/data/ \
  -v /icon_cache/ \
  -p 80:80 \
  vaultwarden/server:latest

Note, that in the above example we don't mount the volume locally, which means it won't be persisted during the upgrade unless you use intermediate data container using --volumes-from. This will impact performance as vaultwarden will have to re-download the icons on restart, but might save you from having stale icons in cache as they are not automatically cleaned.

FAQs

1. FAQs
2. Audits
3. Supporting upstream development

Troubleshooting

1. Logging
2. Bitwarden Android troubleshooting

Container Image Usage

1. Which container image to use
2. Starting a container
3. Using Docker Compose
4. Using Podman
5. Updating the vaultwarden image

Reverse Proxy

1. Proxy examples
2. Using an alternate base dir (subdir/subpath)

HTTPS

1. Enabling HTTPS
2. Running a private vaultwarden instance with Let's Encrypt certs

Configuration

1. Overview
2. Enabling admin page
3. SMTP configuration
4. Disable registration of new users
5. Disable invitations
6. Enabling WebSocket notifications
7. Enabling Mobile Client push notification
8. Other configuration

Database

1. Using the MariaDB (MySQL) Backend
2. Using the PostgreSQL Backend
3. Running without WAL enabled
4. Migrating from MariaDB (MySQL) to SQLite

Security

1. Hardening Guide
2. Password hint display
3. Enabling U2F and FIDO2 WebAuthn authentication
4. Enabling YubiKey OTP authentication
5. Fail2Ban Setup
6. Fail2Ban + ModSecurity + Traefik + Docker

Performance

1. Changing the API request size limit
2. Changing the number of workers

Customization

1. Translating the email templates
2. Translating admin page
3. Customize Vaultwarden CSS
4. Disabling or overriding the Vault interface hosting

Backup

1. General (not docker)
2. Backing up your vault

Development

1. Building binary
2. Building your own docker image
3. Git hooks
4. Differences from the upstream API implementation

Alternative deployments

1. Pre-built binaries
2. Creating a systemd service
3. Third-party packages
4. Deployment examples
5. Disable the admin token

Other Information

1. Importing data from Keepass or KeepassX
2. Changing persistent data location
3. Syncing users from LDAP
4. Caddy 2.x with Cloudflare DNS
5. Logrotate example