Vaultwarden

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

Version Tags

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.

Prerequisites

Before deploying, ensure your host environment is ready. See the Quick Start Guide for host setup instructions.

Deployment

Podman Compose

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"
    # always (not unless-stopped) so FreeBSD's podman rc.d auto-starts it at boot
    restart: always

Save as compose.yaml, then run podman-compose up -d.

AppJail Director

.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}

Save the files above, then run appjail-director up.

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 CLI

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:latest

Save as run.sh, then run sh run.sh.

AppJail

appjail 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 vaultwarden

Save as run.sh, then run sh run.sh.

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.

Bastille

Warning

Bastille's OCI support is experimental. It requires buildah, shares the host network stack (inherit), and persists image-declared volumes under --data-path.

services:
  vaultwarden:
    image: "ghcr.io/daemonless/vaultwarden:latest"
    container_name: vaultwarden
    network_mode: host  # jail shares host networking
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
      - SIGNUPS_ALLOWED=true
      - INVITATIONS_ALLOWED=

Save as podman-compose.yml, then run bastille up. Or via CLI:

bastille create -O \
  --env PUID=1000 \
  --env PGID=1000 \
  --env TZ=UTC \
  --env SIGNUPS_ALLOWED=true \
  --env INVITATIONS_ALLOWED= \
  --data-path /path/to/containers/vaultwarden \
  vaultwarden ghcr.io/daemonless/vaultwarden:latest inherit

Ansible

- 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"

Save as vaultwarden-deploy.yaml, then run ansible-playbook vaultwarden-deploy.yaml.

Access at: http://localhost:80

Parameters

Environment Variables

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)

Volumes

Path	Description
/config	Data directory (database, attachments, icons)

Ports

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.