Lightweight Bitwarden-compatible password manager server — self-host your passwords, secrets, and secure notes.
| Port | 80 |
| Registry | ghcr.io/daemonless/vaultwarden |
| Source | https://github.com/dani-garcia/vaultwarden |
| Website | https://github.com/dani-garcia/vaultwarden |
| Tag | Description | Best For |
|---|---|---|
latest |
Upstream Binary. Built from official release. | Alternative build. |
pkg |
FreeBSD Quarterly. Uses stable, tested packages. | Most users. Matches Linux Docker behavior. |
pkg-latest |
FreeBSD Latest. Rolling package updates. | Newest FreeBSD packages. |
Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions.
services:
vaultwarden:
image: "ghcr.io/daemonless/vaultwarden:latest"
container_name: vaultwarden
environment:
- PUID=1000 # User ID for the application process
- PGID=1000 # Group ID for the application process
- TZ=UTC # Timezone for the container
- SIGNUPS_ALLOWED=true # Enable/disable user registration (true/false)
- INVITATIONS_ALLOWED= # Enable/disable user invitations (true/false)
volumes:
- "/path/to/containers/vaultwarden:/config"
ports:
- "80:80"
restart: unless-stopped.env:
# .env
DIRECTOR_PROJECT=vaultwarden
PUID=1000
PGID=1000
TZ=UTC
SIGNUPS_ALLOWED=true
INVITATIONS_ALLOWED=
appjail-director.yml:
# appjail-director.yml
options:
- virtualnet: ':<random> default'
- nat:
services:
vaultwarden:
name: vaultwarden
options:
- container: 'boot args:--pull'
- expose: '80:80 proto:tcp' \
oci:
user: root
environment:
- PUID: !ENV '${PUID}'
- PGID: !ENV '${PGID}'
- TZ: !ENV '${TZ}'
- SIGNUPS_ALLOWED: !ENV '${SIGNUPS_ALLOWED}'
- INVITATIONS_ALLOWED: !ENV '${INVITATIONS_ALLOWED}'
volumes:
- vaultwarden: /config
volumes:
vaultwarden:
device: '/path/to/containers/vaultwarden'Makejail:
# Makejail
ARG tag=latest
OPTION overwrite=force
OPTION from=ghcr.io/daemonless/vaultwarden:${tag}
Note: Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the IPv4 address assigned by the virtual network.
podman run -d --name vaultwarden \
-p 80:80 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=UTC \
-e SIGNUPS_ALLOWED=true \
-e INVITATIONS_ALLOWED= \
-v /path/to/containers/vaultwarden:/config \
ghcr.io/daemonless/vaultwarden:latestappjail oci run -Pd \
-o overwrite=force \
-o container="args:--pull" \
-o virtualnet=":<random> default" \
-o nat \
-o expose="80:80 proto:tcp" \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=UTC \
-e SIGNUPS_ALLOWED=true \
-e INVITATIONS_ALLOWED= \
-o fstab="/path/to/containers/vaultwarden /config <pseudofs>" \
ghcr.io/daemonless/vaultwarden:latest vaultwardenNote: Exposing ports in AppJail means that your service can be reached from remote hosts. If that is not your intention, do not expose the ports and communicate with the service using the IPv4 address assigned by the virtual network.
- name: Deploy vaultwarden
containers.podman.podman_container:
name: vaultwarden
image: "ghcr.io/daemonless/vaultwarden:latest"
state: started
restart_policy: always
env:
PUID: "1000"
PGID: "1000"
TZ: "UTC"
SIGNUPS_ALLOWED: "true"
INVITATIONS_ALLOWED: ""
ports:
- "80:80"
volumes:
- "/path/to/containers/vaultwarden:/config"Access at: http://localhost:80
| Variable | Default | Description |
|---|---|---|
PUID |
1000 |
User ID for the application process |
PGID |
1000 |
Group ID for the application process |
TZ |
UTC |
Timezone for the container |
SIGNUPS_ALLOWED |
true |
Enable/disable user registration (true/false) |
INVITATIONS_ALLOWED |
`` | Enable/disable user invitations (true/false) |
| Path | Description |
|---|---|
/config |
Data directory (database, attachments, icons) |
| Port | Protocol | Description |
|---|---|---|
80 |
TCP | Web UI |
Architectures: amd64
User: bsd (UID/GID via PUID/PGID, defaults to 1000:1000)
Base: FreeBSD 15
Need help? Join our Discord community.