Instance Generator
Pick a deployment, set your options, and copy the files Arcane needs. The output updates as you go.
Deployment
Jump to outputManager
The Arcane web UI. It manages the container engine on the host it runs on.
Agent
Connects another host to an existing Manager as a remote environment. Create the environment in Arcane first to get its token.
Basics
Image, address, and file ownership.
Where to pull the Arcane manager image from
The URL your browser uses to open Arcane
The host port Arcane is published on
Host user ID that owns files Arcane creates. On rootless Podman, use your own ID (id -u).
Host group ID that owns files Arcane creates. On rootless Podman, use your own group ID (id -g).
Advanced · 1
Volume name for Arcane data
Host access
Choose how Arcane reaches the container engine on this host.
Path to the Docker socket on the host. On a Podman host, use the Podman socket path.
Use a Docker socket proxy container instead of mounting the Docker socket directly
Relabel the projects folder mount, and turn off SELinux labelling when the socket is mounted directly
Advanced · 2
Add the mounts Arcane needs to read host metrics inside an LXC container, such as on Proxmox
Add a health check that runs the built-in arcane health command
Storage
Optional host folder for Compose projects, mounted at the same path inside the container.
Absolute host path to the folder that holds your Compose projects
Runtime
Logging and runtime behavior.
Logging verbosity
Enable JSON formatted logs
IANA timezone for scheduled jobs. The container default is UTC.
Security
The key Arcane uses to encrypt stored secrets.
Encryption key for secure stored sensitive data (auto-generated if empty)
Database
Arcane uses SQLite unless you switch to PostgreSQL.
Authentication
Single sign-on through your OIDC provider.