zot

Production-ready, vendor-neutral OCI image registry with a web UI, image search and vulnerability scanning.

Port	5000
Registry	ghcr.io/daemonless/zot
Source	https://github.com/project-zot/zot
Website	https://zotregistry.dev/

Version Tags

Tag	Description	Best For
latest	Official upstream zot FreeBSD binary (auto-tracks latest release).	Most users — recommended.
pkg	FreeBSD Quarterly. Uses stable, tested packages.	Production stability.
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:
  zot:
    image: "ghcr.io/daemonless/zot:latest"
    container_name: zot
    environment:
      - PUID=1000  # User ID for the registry process
      - PGID=1000  # Group ID for the registry process
      - TZ=UTC  # Timezone for the container
    volumes:
      - "/containers/zot:/config"
      - "/containers/zot/data:/data"
    ports:
      - "5000:5000"
    # 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=zot
PUID=1000
PGID=1000
TZ=UTC

appjail-director.yml:

# appjail-director.yml

options:
  - virtualnet: ':<random> default'
  - nat:
services:
  zot:
    name: zot
    options:
      - container: 'args:--pull'
      - expose: '5000:5000 proto:tcp'
    oci:
      user: root
      environment:
        - PUID: !ENV '${PUID}'
        - PGID: !ENV '${PGID}'
        - TZ: !ENV '${TZ}'
    volumes:
      - zot: /config
      - zot_data: /data
volumes:
  zot:
    device: '/containers/zot'
  zot_data:
    device: '/containers/zot/data'

Makejail:

# Makejail

ARG tag=latest

OPTION container=boot
OPTION overwrite=force
OPTION from=ghcr.io/daemonless/zot:${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.

Bastille

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:
  zot:
    name: zot
    image: "ghcr.io/daemonless/zot:latest"
    network:
      - mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=UTC
    volumes:
      - "/containers/zot:/config"
      - "/containers/zot/data:/data"

Save as bastille-compose.yml, then run bastille up. Open http://<server>:5000 from another machine (the server's own browser can't use a published port).

Parameters

Environment Variables

Variable	Default	Description
PUID	1000	User ID for the registry process
PGID	1000	Group ID for the registry process
TZ	UTC	Timezone for the container

Volumes

Path	Description
/config	Configuration (config.json, written with a working default on first start)
/data	Image storage and the registry's metadata database

Ports

Port	Protocol	Description
5000	TCP	Registry API and web UI

Architectures: amd64, aarch64 User: bsd (UID/GID via PUID/PGID, defaults to 1000:1000) Base: FreeBSD 15.1

---

Need help? Join our Discord community.