Arcane 3.0.1: A Self-Hosted Docker Control Plane With a Root-Level Warning
Docker Compose is easy to understand when a project has one service. It becomes less pleasant when a server accumulates databases, workers, reverse proxies, backups, and several stacks that need updates. You can keep using the CLI, but the operational picture starts spreading across terminal sessions and folders.
Arcane is a self-hosted web interface for managing that environment. Its recent v3 release makes it worth evaluating, especially if you want a visual control plane without moving your containers to a hosted service.
There is one important warning before the screenshots: a tool with access to the Docker socket has serious host-level power. Arcane is convenient, but it must be deployed like privileged infrastructure.
What Arcane does
Arcane provides a web UI for Docker containers, Compose projects, images, volumes, backups, and update workflows. Its documentation also covers remote hosts and Swarm, Podman, user roles, passkeys, single sign-on, a mobile app, and an API.
A project in Arcane is still a directory containing a Compose file and its related configuration. Arcane does not replace Compose. It gives you a place to inspect, edit, deploy, and monitor those projects. The source repository is BSD-3-Clause licensed. In a self-hosted deployment, your practical costs are infrastructure, storage, backups, and maintenance.
Official Arcane v3 dashboard screenshot. Source: Arcane repository assets.
The project appeared at position 6 in a GitHub daily Trending snapshot collected at 06:57 UTC on November 17, with 46 stars shown for that day. GitHub's repository API showed 9,015 stars at 10:47 UTC. The project had released v3.0.0 on November 14 and v3.0.1 on November 15. A recent r/homelab discussion comparing Dockge and Arcane also shows that people are evaluating it in the self-hosting community, although a discussion thread is not proof of broad adoption.
What changed in v3.0.1?
The v3.0.1 release notes are more operational than flashy. They describe fixes for agent-mode startup and performance, stricter certificate and update verification, Docker disk-usage timeouts, Swarm behavior, Git-synced environment files, and backup startup.
That is useful context for teams running multiple hosts. A management UI is only valuable if the agent and manager stay in sync and routine operations do not become a source of downtime.
The v3 migration is not a casual image-tag change. The official migration guide says to upgrade a v2 installation to 2.17.3 first, start the manager and every agent once, back up the database and project files, then update the manager and agents together to v3.0. It also calls out renamed environment variables. Read the guide before changing an existing production installation.
Project logo from the official Arcane assets.
Install a fresh instance
The documented Docker Compose path requires Docker Engine and Docker Compose. First generate an encryption key:
docker run --rm ghcr.io/getarcaneapp/manager:latest /app/arcane generate secret Copy the generated value. Create a compose.yaml file:
services: arcane: image: ghcr.io/getarcaneapp/manager:latest container_name: arcane ports: - "3552:3552" volumes: - /var/run/docker.sock:/var/run/docker.sock - arcane-data:/app/data - /opt/docker:/opt/docker environment: - ARCANE_APP_URL=http://localhost:3552 - PUID=1000 - PGID=1000 - ARCANE_ENCRYPTION_KEY=replace-with-generated-key - ARCANE_PROJECTS_DIRECTORY=/opt/docker cgroup: host restart: unless-stopped volumes: arcane-data: Replace the encryption-key value. The official guide requires a passphrase of at least 32 characters. Change the URL if you will access Arcane from another device, and make sure the host projects directory is mounted at the same absolute path inside the container.
Start it:
docker compose up -d docker compose cp arcane:/app/data/initial-admin-password . The second command copies the generated initial admin password from the container. Use it for the first login and then set a new password.
This gives you a local instance on port 3552. Before exposing it outside your machine, configure TLS, access controls, and a network boundary.
The Docker socket is the real security decision
The standard installation mounts:
/var/run/docker.sock:/var/run/docker.sock That socket gives Arcane access to the Docker API. The Arcane security documentation explicitly warns that creating containers can allow a user to mount the host filesystem or run a privileged container. In practical terms, someone who can control this Arcane instance may be able to take over the Docker host.
A read-only mount of the socket file does not make Docker API requests read-only. A socket proxy can restrict which API routes are exposed, but it does not turn container creation into a harmless operation.
Use Arcane only on a trusted host, keep its login and API keys private, restrict network access, and consider the documented socket-proxy setup. Do not treat the dashboard as a low-privilege convenience app.
Where it fits
| Tool | Better fit |
|---|---|
| Arcane | Self-hosted management across Docker projects and remote hosts, with a modern UI |
| Dockge | A focused interface for managing Compose stacks |
| Portainer | A broader container-management platform with a mature ecosystem and additional deployment options |
| Docker CLI and Compose | Minimal dependencies, explicit automation, and infrastructure-as-code workflows |
Arcane is attractive when you want to see containers and Compose projects together. It is less compelling if you already have a GitOps workflow that deliberately keeps production changes outside a web dashboard.
A few features also deserve caution. The documentation marks container-to-Compose conversion as experimental. The separate CLI is described as early in development. Treat those features as optional until they have been tested against your own setup.
Who should try it?
Arcane is a reasonable candidate for homelab operators, small teams with a few Docker hosts, and developers who maintain several Compose-based services. It is not a replacement for Kubernetes orchestration, a backup strategy, or a secure deployment pipeline.
For a new test instance, follow the official installation guide. For an existing v2 server, follow the migration guide in order. The official site also provides a demo, so you can inspect the interface before giving it access to a real Docker socket.
Sources and further reading
- Arcane GitHub repository
- Official installation guide
- Migrate an existing installation to v3
- Docker socket proxy and security warning
- v3.0.1 release notes
- Arcane official demo
- r/homelab Dockge vs Arcane discussion
Would you trust a web dashboard with Docker socket access on your main server, or would you keep it isolated on a separate management host?
Written by Sh Raj. More engineering notes: LinkedIn · StackShade on YouTube.


