Preview Builds
Try unreleased Arcane changes with the next image tags.
Preview builds (next builds) come from the main branch before a stable release.
Use a preview build
Section titled “Use a preview build”-
In
compose.yaml, change the image tag tonext:- Manager:
ghcr.io/getarcaneapp/manager:next - Agent:
ghcr.io/getarcaneapp/agent:next
- Manager:
-
Recreate the container:
Terminal window docker compose up -d
To pin one preview build, use its versioned tag, such as ghcr.io/getarcaneapp/manager:v3.1.0-next.1.
When a newer next build is available, What’s new in the update dialog lists the commits between your build and the new one, grouped by type, and links to the comparison on GitHub.
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:Switch off development branding
Section titled “Switch off development branding”Non-release builds show a development icon for the logo, favicon, and app icons. A non-release build is any version other than a plain release like v3.1.0.
- Open System → Branding.
- Turn off Development Branding. This needs
settings:update.
Uploading your own logo and icons also replaces the development artwork.
Download a binary
Section titled “Download a binary”Report a problem
Section titled “Report a problem”Open an issue on GitHub Issues. Include the version number shown on your dashboard.
Image tags
Section titled “Image tags”| Tag | Points to |
|---|---|
next |
The latest build from main. |
Versioned, v3.1.0-next.1 |
That specific build (v3.1.0-next.1, .2, etc.). |
Preview images run static binaries on Arcane’s distroless base image, a minimal image with no shell or package manager.