Public | Automated Build

Last pushed: 3 years ago
Short Description
Short description is empty for this repo.
Full Description

Dockerized Mumble Server


  • Install Docker.
  • If on Mac OS X, or any other platform which tends to only have a Docker client, you'll also need a Docker daemon running remotely, exposing the API.
  • This can also easily be run on a Docker Swarm cluster.


There are two example configuration files in this repository, if you don't already have one, that you can copy and modify to your liking. Once you've done that, you can create a data-container to hold your configuration file:

$ docker run -i --name mumble-conf --entrypoint /bin/bash tmaddox/murmur:1.0 -c 'cat > ./mumble-server.ini' < ./mumble-server.ini

Once that's done, you can start the service like so:

$ docker run -d --restart always --name mumble-server --volumes-from mumble-conf -p $DESIRED_HOST_PORT:64738 tmaddox/murmur:1.0

Configure while running

Because the volume used in this image (/var/lib/mumble-server) includes the Mumble database that persists things like your superuser password, channel configurations, access controls, etc., you can run commands against the Mumble binary that will make updates to this database for your running server.

For example, here's how you can set your SuperUser password on your running Mumble server.

$ docker run -i --rm --volumes-from mumble-conf murmur:1.0 -supw secret_to_guard_the_precious

Migrating existing Mumble server

In order to migrate from an existing server, you'll need a copy of the source server's SQLite database file (usually found at /var/lib/mumble-server/mumble-server.sqlite). Once you have that, place it and your mumble-server.ini in a directory together.

For example, I have a directory mumble-server-conf with both a mumble-servver.ini and a mumble-server.sqlite from an old mumble-server deploy:

$ tar -cv mumble-server-conf/* | docker run -i --name mumble-conf --entrypoint /bin/bash tmaddox/murmur:1.0 -c 'tar -xv'

This created my mumble-conf data container, created an archive via tar cv mumble-server-conf/*, and then piped it through STDIN to be extracted inside mumble-conf's working directory (/var/lib/mumble-server).

If it worked properly you should see output like the following:


Now, I can just start the server like normal, but this time it's using the mumble-conf data container and the generic tmaddox/murmur:1.0 image. :smile:

$ docker run -d --restart always --name mumble-server --volumes-from mumble-conf -p $DESIRED_HOST_PORT:64738 tmaddox/murmur:1.0

Sláinte! :beers:

Docker Pull Command
Source Repository