-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Building your own docker image
BlackDex edited this page Nov 8, 2023
·
6 revisions
Clone the repository, then from the root of the repository run to build with default sqlite backend:
Please read the documentation provided in the docker directory for the latest information on how to build Vaultwarden locally.
This can be done via docker or podman. See: https://github.com/dani-garcia/vaultwarden/tree/main/docker
# Build the docker image with all databases supported:
docker buildx build -t vaultwarden .
To build with SQLite backend only run:
# Build the docker image:
docker buildx build -t vaultwarden --build-arg DB=sqlite .
To build with MySQL backend only run:
# Build the docker image:
docker buildx build -t vaultwarden --build-arg DB=mysql .
To build with Postgresql backend only run:
# Build the docker image:
docker buildx build -t vaultwarden --build-arg DB=postgresql .
in docker-compose.yml it looks like
vaultwarden:
image: vaultwarden
build:
context: vaultwarden
args:
DB: postgresql
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- 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