dankhostself-host anything

Portainer CE with Docker Compose

Portainer Community Edition is a free, lightweight container management UI for Docker, Swarm, Podman, Kubernetes, and ACI environments. In the project's words: Portainer README on GitHub checked 2026-09-26

Runs on: amd64, arm64, arm/v7, ppc64le, windows/amd64 from each image's registry manifest, checked 2026-09-26; a CPU counts only if every image has a build for it. Image by image

Add Portainer CE to the builder to use your own domain and combine it with other apps in one file.

What Portainer CE needs

Only figures Portainer CE's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.

ResourceMinimumRecommended
RAMThe project publishes no figure
CPUThe project publishes no figure
DiskThe project publishes no figure

On top of this, Caddy (the reverse proxy in the file) is a single small container.

Which hardware Portainer CE has images for

Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.

  • x86-64 PC or NAS (linux/amd64): every image has a build.
  • Raspberry Pi 4/5, 64-bit OS (linux/arm64): every image has a build.
  • Raspberry Pi 3 or Zero 2 W, 32-bit OS (linux/arm/v7): every image has a build.
ServiceImagePlatforms in the manifestDigestRegistryChecked
portainerportainer/portainer-ce:ltsamd64, arm64, arm/v7, ppc64le, windows/amd64sha256:4d616db18cfeb5dd41a69c0958bc825c84483ea9cde1106eb82a5d26f3bd8b0eregistry-1.docker.io2026-09-26

A manifest says an image exists for a CPU, not how well Portainer CE runs on it: a build for arm64 or arm/v7 can still be too slow or need more memory than the board has. The RAM and disk Portainer CE publishes are in the table above and, for a whole set of apps against a Raspberry Pi, on Will it run on my machine?. A tag like latest can move to a new digest after the date checked.

docker-compose.yml

This is exactly what the builder writes for Portainer CE alone on example.org: the official definition with its published ports removed and Caddy added in front.

# docker-compose.yml built at dankhost.com for: Portainer CE
# Each app block is its official compose definition. Only the names were prefixed with
# the app slug (services, containers, volumes, bind folders, .env variables) so any set of
# apps can share one file; other differences are listed under "Changed:" in each block.
# Only Caddy publishes ports. Secrets live in .env next to this file.

services:
  # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ----
  # Source: https://caddyserver.com/docs/running (checked 2026-09-23)
  # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23)
  # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly.
  caddy:
    image: "caddy:2"
    container_name: "caddy"
    restart: "unless-stopped"
    ports:
      - "80:80"
      - "443:443"
      - "443:443/udp"
    volumes:
      - "./caddy:/etc/caddy"
      - "caddy-data:/data"
      - "caddy-config:/config"
    networks:
      proxy:
        ipv4_address: "172.30.0.2"

  # ---- Portainer CE (portainer.example.org) ----
  # Source: https://docs.portainer.io/start/install-ce/server/docker/linux (checked 2026-09-26)
  # Source: https://docs.portainer.io/faqs/installing/setup-token (checked 2026-09-26)
  # Source: https://docs.portainer.io/advanced/reverse-proxy (checked 2026-09-26)
  # Changed: Removed the '9443:9443' and '8000:8000' ports: Caddy reaches Portainer's plain-HTTP port 9000 inside the container (the page's "-p 9000:9000" for legacy reasons). 8000 is only for Edge Agents, as the file's comment says.
  #          The fixed volume name portainer_data and network name portainer_network are left out, so the volume carries the portainer- prefix like every other.
  # ELEVATED ACCESS (Docker socket): /var/run/docker.sock is mounted read-write, as on Portainer's install page: that is how Portainer manages Docker, and control of the Docker socket is the same power as root on this server. Anyone who can log in to Portainer as an administrator can start a container that reads every file on the host.
  portainer:
    image: "portainer/portainer-ce:lts"
    container_name: "portainer"
    restart: "always"
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "portainer-portainer_data:/data"
    networks:
      proxy: {}

networks:
  # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact.
  # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's
  # ipv4_address and in every trusted-proxy value to a free 172.x.0 range.
  proxy:
    ipam:
      config:
        - subnet: "172.30.0.0/24"
          ip_range: "172.30.0.128/25"
          gateway: "172.30.0.1"

volumes:
  caddy-data:
  caddy-config:
  portainer-portainer_data:

Caddyfile save as caddy/Caddyfile

Caddy gets and renews the HTTPS certificate for portainer.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.

# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.

# Portainer CE
portainer.example.org {
	reverse_proxy portainer:9000
}

Already running nginx, Nginx Proxy Manager, Caddy or Traefik? The reverse-proxy settings Portainer CE needs, for all four, each cited to Portainer CE's own docs.

.env

Portainer CE needs no secret here; the builder adds nothing you have to fill in by hand.

# .env for Portainer CE, from dankhost.com/app/portainer/. Nothing here is secret.
# Keep this file private (chmod 600).
# None of the chosen apps needs a variable here.

What Portainer CE needs beyond the proxy

Portainer CE asks for more than an ordinary container. The compose file keeps what the project documents and labels each item with an # ELEVATED ACCESS comment; /check/ flags it too, as it would in any file.

  • Docker socket: /var/run/docker.sock is mounted read-write, as on Portainer's install page: that is how Portainer manages Docker, and control of the Docker socket is the same power as root on this server. Anyone who can log in to Portainer as an administrator can start a container that reads every file on the host.

Changes from the official file

Besides prefixing every service, container, volume, folder and variable with portainer (so any set of apps can share one file), these are all the differences from what the project documents:

  • Removed the '9443:9443' and '8000:8000' ports: Caddy reaches Portainer's plain-HTTP port 9000 inside the container (the page's "-p 9000:9000" for legacy reasons). 8000 is only for Edge Agents, as the file's comment says.
  • The fixed volume name portainer_data and network name portainer_network are left out, so the volume carries the portainer- prefix like every other.

Notes for Portainer CE behind the proxy

  • Within 5 minutes of the first start, open https://portainer.example.org and create the admin user with the setup token from the logs: docker compose logs portainer | grep setup_token. Portainer's setup-token page says the token is one-time and the user must be created within 5 minutes; after that, restart Portainer to try again.
  • Caddy passes the original Host and X-Forwarded-Proto: https, which Portainer's reverse-proxy page says it uses for its Secure login cookie and its CSRF check.
  • Portainer controls Docker on this server with root-equal power (see the ELEVATED ACCESS line in the compose file). Use a long admin password; picking Authelia in the builder puts its login in front of Portainer's too.

How to run it

  1. At your DNS provider, add an A record named portainer on your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it.
  2. Save the three files in one folder: docker-compose.yml and .env side by side, the Caddyfile at ./caddy/Caddyfile. Replace example.org with your domain in the Caddyfile, the compose file and the .env, or let the builder do it.
  3. Nothing in .env needs filling in; chmod 600 .env all the same.
  4. Start it:
    docker compose up -d
    docker compose logs -f caddy   # watch the certificate arrive
  5. Open the new address (portainer. plus your domain) in a browser and follow the notes above.

Back it up

Portainer keeps its database, settings and stacks in the portainer_data volume at /data; the Docker socket belongs to the host.

Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.

# BACKUP.md built at dankhost.com for: Portainer CE

What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.

The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.

Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.

## Before you start

    BACKUP=/mnt/backup/selfhost   # change this: a disk or machine other than this server's system disk
    mkdir -p "$BACKUP"

## Every time: the three stack files

    tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy

.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.

## Caddy (the reverse proxy)

Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.

- caddy-data (named volume, /data in caddy)
  BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
  SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
  IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.

Copy (Caddy keeps serving while you copy):

    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data

Restore check:

    tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
    docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"

Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)

## Portainer CE

Portainer keeps its database, settings and stacks in the portainer_data volume at /data; the Docker socket belongs to the host.

What this compose mounts:
- /var/run/docker.sock (/var/run/docker.sock in portainer)
  SKIP: the host's Docker socket, not Portainer data.
- portainer-portainer_data (named volume, /data in portainer)
  BACK UP: Portainer's database: users, settings, environments and the stacks you created.

1. Stop portainer. Stopping it keeps its database from changing mid-copy. The containers it manages keep running.

    docker compose stop portainer

2. Copy while portainer is stopped:

    docker run --rm --volumes-from portainer -v "$BACKUP":/backup ubuntu tar cvf /backup/portainer-portainer_data.tar /data

3. Start it again:

    docker compose start portainer

Restore check:

    tar tf "$BACKUP/portainer-portainer_data.tar" > /dev/null && echo OK

Put a copy back (with portainer stopped):

    docker run --rm --volumes-from portainer -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/portainer-portainer_data.tar --strip 1"

Stop it, put the volume back with the command above, start it.

Sources:
- Portainer docs: Install Portainer CE with Docker on Linux (compose file, ports 9443, 8000, 9000): https://docs.portainer.io/start/install-ce/server/docker/linux (checked 2026-09-26)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-26)

Update it

What docker compose pull does depends only on how each image line in the compose file above is tagged. For Portainer CE as this page writes it:

ServiceImageHow it is pinnedWhat docker compose pull does
caddycaddy:2Major version only (tag 2)Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit.
portainerportainer/portainer-ce:ltsNot pinned: moving tag ltsMoves to the newest image published as lts, which can be a new major version.

What Portainer CE's docs say about updating

Portainer's upgrade page: take a backup of the Portainer configuration before any update, pull the new portainer/portainer-ce:lts image and recreate the container.

  • Coming from Portainer 1.x, update to 2.0.0 first, then to the newest version.

Source: Portainer docs: Updating on Docker Standalone checked 2026-09-30

The steps

  1. Back up first, as in Back it up above. An update can migrate Portainer CE's data on its first start; the copy is the way back.
  2. Download the new images. Running containers are not touched yet:
    docker compose pull
  3. Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
    docker compose up -d
  4. Watch Portainer CE start (Ctrl+C stops following the log, not the app):
    docker compose logs -f portainer
  5. Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
    docker image prune

Docker's reference for these commands: Docker docs: docker compose pull checked 2026-09-30; Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30; Docker docs: docker image prune checked 2026-09-30

Locked out? Reset the admin password

Portainer's helper image sets a new random password for the admin user and prints it. If it finds no admin, it creates one (admin, or admin-<random> if that name is taken).

  1. Stop Portainer. Source: Portainer docs: Reset the admin user's password (Method 1, helper-reset-password) read 2026-10-03; Docker docs: docker compose stop read 2026-10-03
    docker compose stop portainer
  2. Run the helper with Portainer's data. The docs mount the volume at /data; --volumes-from gives the helper the same mounts as the portainer container, which has its data at /data. Source: Portainer docs: Reset the admin user's password (Method 1, helper-reset-password) read 2026-10-03; Docker docs: Volumes, Back up, restore, or migrate data volumes (--volumes-from) read 2026-10-03
    docker run --rm --volumes-from portainer portainer/helper-reset-password
  3. Copy the password it prints, start Portainer and log in. Source: Portainer docs: Reset the admin user's password (Method 1, helper-reset-password) read 2026-10-03; Docker docs: docker compose start read 2026-10-03
    docker compose start portainer

Run the commands in the folder that holds docker-compose.yml.

Sources

Every page below was fetched on the date shown.

Add Portainer CE to the builder All one hundred apps

Made with AI tools. ยท Privacy