goofball222 / mumo

Docker container for "mumo" scripts from https://mumble.info

Mumble Mumo Docker Container

Docker tags:

Tag	Description	Release Date
latest	Latest stable release	2021-06-17
1.1.0	Static stable release tag/image	2021-06-17

---

• Recent changes, see: GitHub CHANGELOG.md
• Report any bugs, issues or feature requests on GitHub

---

Usage

This container exposes two volumes:

• /opt/mumo/config - Mumo and module configuration - REQUIRED: this must be mapped to a persistent volume or the container will not work.
• /opt/mumo/logs - Mumo logs for troubleshooting

This container exposes NO PORTS. It must be connected to the Murmur server container via Docker container network sharing.

---

The most basic way to run this container:

$ docker run --name mumo -d \
    --net=container:<murmur container id> \
    -v ./config:/opt/mumo/config  \
    goofball222/mumo

---

Recommended: run via Docker Compose:

Have the container store the config & logs on a local file-system or in a specific, known data volume (recommended for persistence and troubleshooting), bring up in concert with Murmur:

version: '3'

services:
  murmur:
    image: goofball222/murmur
    container_name: murmur
    ports:
      - 64738:64738
      - 64738:64738/udp
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./data:/data
      - ./murmur.ini:/etc/murmur.ini
    environment:
      - TZ=UTC

  mumo:
    image: goofball/mumo
    container_name: mumo
    network_mode: service:murmur
    depends_on:
      - murmur
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/opt/mumo/config
      - ./log:/opt/mumo/log
    environment:
      - TZ=UTC

Example docker-compose.yml file

---

Environment variables:

Variable	Default	Description
DEBUG	false	Set to true for extra entrypoint script verbosity for debugging
MUMO_OPTS	unset	Any additional custom run flags for the container mumo.py script
PGID	999	Specifies the GID for the container internal mumo group (used for file ownership)
PUID	999	Specifies the UID for the container internal umumo user (used for process and file ownership)
RUN_CHOWN	true	Set to false to disable the container automatic chown at startup. Speeds up startup process on overlay2 Docker hosts. NB/IMPORTANT: It's critical that you insure directory/data permissions on all mapped volumes are correct before disabling this or mumo will not start.
RUNAS_UID0	false	Set to true to force the container to run the mumo.py script as UID=0 (root) - NB/IMPORTANT: running with this set to "true" is insecure

---