Preview Builds

Try unreleased Arcane changes with the next image tags.

Preview builds, also called next builds, are built automatically from Arcane’s main branch and include changes that haven’t reached a stable release. Use them to try new features or confirm a fix before it ships, on a test instance rather than one you depend on.

Use a preview build

Change the image tag in your compose.yaml from latest (or your current tag) to next, then run docker compose up -d.

Manager:

ghcr.io/getarcaneapp/manager:next

Agent:

ghcr.io/getarcaneapp/agent:next

For example:

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:
      - APP_URL=http://localhost:3552
      - ENCRYPTION_KEY=<your-encryption-key>
    restart: unless-stopped

volumes:
  arcane-data:

Development branding

Preview builds, and any other build whose version isn’t a plain release such as v2.4.0, use a development icon in place of the Arcane logo, favicon, and app icons. To show the standard logo instead, click the version number at the bottom of the sidebar and switch off Development Branding (requires settings:write).

Download a binary

Next Binaries

Report a problem

Report problems with preview builds on GitHub Issues. Include the version shown on your dashboard so we can identify the build.

Reference

Preview images use static binaries on Arcane’s distroless runtime base (a minimal image with no shell or package manager). Every build is published under three tags:

Tag	Points to
`next`	The most recent build.
`next-static`	Same as `next`, kept for existing setups.
Versioned, `v2.4.0-next.1`	That specific build, permanently.

Versions count up toward the next release: v2.4.0-next.1, v2.4.0-next.2, and so on until v2.4.0 ships.