Preview Builds

Try unreleased Arcane changes with the next image tags.

Run preview builds (also called next builds) on a test instance to try new features or verify fixes from the main branch before a stable release.

Use a preview build

Change the image tag in your compose.yaml to next.

Manager:

ghcr.io/getarcaneapp/manager:next

Agent:

ghcr.io/getarcaneapp/agent:next

Example compose.yaml:

services:
  arcane:
    image: ghcr.io/getarcaneapp/manager:next
    container_name: arcane
    ports:
      - '3552:3552'
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - arcane-data:/app/data
    environment:
      - ARCANE_APP_URL=http://localhost:3552
      - ARCANE_ENCRYPTION_KEY=<your-encryption-key>
    restart: unless-stopped

volumes:
  arcane-data:

Recreate the container:

docker compose up -d

Switch off development branding

Non-release builds (any version other than a plain release like v2.4.0) display a development icon for the logo, favicon, and app icons. To restore the standard logo, click the version number at the bottom of the sidebar and turn off Development Branding (requires settings:write).

Download a binary

Next Binaries

Report a problem

Open an issue on GitHub Issues and include the version number shown on your dashboard.

Image tags

Preview images run static binaries on Arcane’s distroless base image (a minimal image without a shell or package manager).

Tag	Points to
`next`	The latest build from `main`.
`next-static`	Alias for `next`, kept for existing setups.
Versioned, `v2.4.0-next.1`	That specific build (`v2.4.0-next.1`, `.2`, etc.).