Run Starling with Docker
Starling is the current Fancy Mumble server. With Docker installed and running, start its published image directly. For an existing deployment, follow Migrating to Starling.
Start a server
Section titled “Start a server”docker run -d --name starling --restart unless-stopped -p 64738:64738/tcp -p 64738:64738/udp -p 8080:8080 -p 64740:64740 -v starling-data:/var/lib/starling ghcr.io/fancy-mumble/starling:latestThe same command works in PowerShell. Docker downloads the image automatically; its default starts all services in one container.
Connect Fancy Mumble to localhost:64738. On first boot Starling creates a self-signed server certificate and a SuperUser password. Run docker logs starling to find the password and save it. The starling-data volume preserves the generated configuration, certificate, accounts, channels, and service data.
Configure and operate
Section titled “Configure and operate”The container generates a starter configuration on first run. See Configuration for changing settings. Set a public file-server URL that other members can reach before sharing files outside your machine. See Ports and networking for remote access and feature-specific media ports.
docker logs -f starlingdocker stop starlingdocker start starlingStopping or removing the container keeps its named data volume. Deleting starling-data deletes its configuration, certificate, and databases. See Upgrade and backup.
Distributed deployment or source builds
Section titled “Distributed deployment or source builds”Use the repository’s Compose deployment when you want separate services or a local source build:
git clone https://github.com/Fancy-Mumble/starling.gitcd starlingEdit deploy/starling.toml for the distributed stack. To use the published image, set STARLING_IMAGE=ghcr.io/fancy-mumble/starling:latest in a .env file, then run docker compose up -d --wait. To build locally, run docker compose up -d --wait --build.
The Compose starling service is the single-container alternative: docker compose up -d --wait starling starts it instead of the distributed services. It uses the same deploy/starling.toml mount with service routing overrides; see the Compose file for its mounts and settings.