Traefik Manager

Appearance

SupportStar

Beta ​

The :beta image tracks the dev branch, so it carries the next release before it ships. You get fixes early, and bugs get caught before they reach everyone else.

Switch to beta ​

yaml
image: ghcr.io/chr0nzz/traefik-manager:beta
bash
docker compose pull traefik-manager && docker compose up -d traefik-manager

Agents have a :beta tag too (ghcr.io/chr0nzz/traefik-manager-agent:beta). Keep the Host and its agents on the same channel.

Roll back ​

yaml
image: ghcr.io/chr0nzz/traefik-manager:latest
bash
docker compose pull traefik-manager && docker compose up -d traefik-manager

Your manager.yml and backups are untouched by the switch, in either direction.

Before you switch ​

dev is where fixes land the day they are written, so a beta image can be newer than any testing it has had:

  • Take a backup first, from Settings - Backups, or copy your config directory
  • Expect the occasional rough edge. Anything that reaches :latest has been through a release
  • A new setting written by a beta may not be understood by the older :latest build if you roll back

Reporting ​

The useful bug report says what you did, what happened, and what you expected. Beyond that:

  • Logs from the moment it broke - docker compose logs traefik-manager - are worth more than a description of the error
  • Your version, from Settings - About
  • Your setup where it is relevant: reverse proxy in front, agents, OIDC provider, CrowdSec

Open an issue, or start a discussion if you are unsure whether something is a bug.

Testing a specific fix ​

A fix often lands on dev and needs confirming before release: pull :beta and try the exact thing that failed. That confirmation is the difference between a fix that is believed to work and one that is known to.

Switching over for one test and rolling back afterwards is a perfectly good way to help.

What is in it ​

The release notes cover each release. For what is on dev right now, the commit history is the source of truth.