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 — recommended. |
pkg-latest |
FreeBSD Latest. Rolling package updates. | Staying current. |
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:
- "/containers/vaultwarden:/config"
ports:
- "80:80"
# always (not unless-stopped) so FreeBSD's podman rc.d auto-starts it at boot
restart: alwaysSave as compose.yaml, then run podman-compose up -d.
.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: '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: '/containers/vaultwarden'Makejail:
# Makejail
ARG tag=latest
OPTION container=boot
OPTION overwrite=force
OPTION from=ghcr.io/daemonless/vaultwarden:${tag}
Save the files above, then run appjail-director up.
Warning
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 jail's IPv4 address or hostname assigned by the virtual network.
To avoid exposing ports, just remove the expose option in your appjail-director.yml or from your command-line arguments.
Warning
Bastille's OCI support is experimental. It requires buildah and shares the host network stack (inherit). Mount volumes with --volume HOST JAIL; without it, image-declared volumes are stored under ${bastille_volumesdir}/${jail}.
services:
vaultwarden:
name: vaultwarden
image: "ghcr.io/daemonless/vaultwarden:latest"
network:
- mode: host
environment:
- PUID=1000
- PGID=1000
- TZ=UTC
- SIGNUPS_ALLOWED=true
- INVITATIONS_ALLOWED=
volumes:
- "/containers/vaultwarden:/config"Save as bastille-compose.yml, then run bastille up.
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.