All config environment variables are ignored about mumble-docker HOT 13 CLOSED

Additional underscores in the variable names are ignored (see README)

from mumble-docker.

@azlux do you have an idea? I don't have any experience with docker compose.

@BorisBrock could you try running the container manually to see if the result remains the same?

from mumble-docker.

@Krzmbrzl Starting the container without Docker Compose actually works. In that case the environment variables are applied as expected.

from mumble-docker.

Interesting. In that case my suspicion would be that for some reason docker compose doesn't set the environment variables as expected 🤔

from mumble-docker.

@BorisBrock Do you find your ENV into the output of docker inspect <container runn ID (can be found with docker ps | grep mumble)>

from mumble-docker.

Shouldn't the environment variable be MUMBLE_CONFIG_WELCOMETEXT not MUMBLE_CONFIG_WELCOME_TEXT (note the removed space)?

from mumble-docker.

Hello,

I tried a modification of @BorisBrock and the welcome message works fine, but I had issues with a volume mount and default channels.

When I try to bring the container up, I get a permission error of:

2022-10-06T02:25:12.742473486Z /entrypoint.sh: line 77: /data/mumble_server_config.ini: Permission denied
2022-10-06T02:25:20.061774974Z /entrypoint.sh: line 77: /data/mumble_server_config.ini: Permission denied

My host user has the ID of 1000 and I even specified the PUID/GUID in the compose file but it still makes everything as root.

So then for testing, I sudo chmod 777 data/mumble and everything starts to work but there are no other channels than root.

My compose file is shown below:

services:
  murmur:
    container_name: murmur
    image: mumblevoip/mumble-server:latest
    restart: unless-stopped
    ports:
      - "49155:50051/tcp"
      - "64738:64738/tcp"
      - "64738:64738/udp"
    environment:
       MUMBLE_CONFIG_SERVER_PASSWORD: "mypassword"
       MUMBLE_CONFIG_WELCOME_TEXT: "Howdy Ya'll This is a Mumble Server"
       MUMBLE_CONFIG_USERS: "8"
       MUMBLE_CONFIG_BANDWIDTH: "128000"
       MUMBLE_CONFIG_channelname: "lobby"
       MUMBLE_CONFIG_channelname: "hello"
       MUMBLE_CONFIG_defaultchannel: "2"
       PUID: "1000"
       GUID: "1000"
    volumes:
      - "./data/mumble:/data:rw"

from mumble-docker.

but there are no other channels than root.

Yes that is to be expected. You can't add channels via the INI file. That's currently a limitation of the Mumble server config system and unrelated to the Docker image itself.

As for why everything is created as root, idk 🤷

from mumble-docker.

My host user has the ID of 1000 and I even specified the PUID/GUID in the compose file but it still makes everything as root.

Had the same Permission Denied issue. I don't know if the MUMBLE_UID/MUMBLE_GID environment variables work (I excluded them after realizing that). Since I already had my host user as 1000/1000, I set MUMBLE_CONFIG_UNAME as the same host username and the volume bind started working correctly. No chmod necessary.

Having a working MUMBLE_UID/MUMBLE_GID and being able to set a timezone, all using environment variables, would be a welcome change.

from mumble-docker.

The UID and GID options are for building the image only. Are you aware of that?

from mumble-docker.

The UID and GID options are for building the image only. Are you aware of that?

I was not. Then I assume the PUID/GUID options in the above compose file wouldn't work either?

from mumble-docker.

I don't know what these options are and how they are supposed to work. What I can tell you is that afaik these options are not handled by our docker image. Whatever they do, they have to be handled elsewhere 👀

from mumble-docker.

Closing this as resolved

from mumble-docker.