Murmur (Mumble server) container

[coppit]

Since nativedude created a "competing" container instead of contributing to mine, I've just deleted mine. Use his instead. Or use Discord. That's what I'm using now.

 

I've put together a Murmur container. Murmur is the server component of the Mumble voice-over-ip program.

 

https://registry.hub.docker.com/u/coppit/mumble-server/

 

In the coming days I'll clean it up and put it into a template repository to make it easier for unRAID folks to use it.

 

 

Edited March 30, 2017 by coppit

[Spydawg]

Great!

 

Been looking for it..

 

Thanks

[Dase]

Thanks for creating this container! I have been looking forward to running a Mumble server on my unRAID box.

[coppit]

I put it into my template repository.

 

Add this URL to the templates section of the Docker tab: https://github.com/coppit/docker-templates

 

Then create a new container, selecting mumble-server

[hodkenneth]

Thanks for your work.

 

I had a few questions. for some reason I'm getting "Connection Refused". Which makes me want to assume the ports are off. Even when connecting to a server on the local network. Any advice? 10.0.0.*** 64738 is what its saying. Do I have to change anything in the config file?

 

Thanks, Kenny.

[Nativedude]

Oh good it's not just me then

Same issue, can't get Mumble to connect

[coppit]

I changed the port to 61738 and it started working again.

[dirtysanchez]

When I first set up this container it was unable to connect as well. I went into the container settings and clicked save (without changing anything) which effectively rebuilds the container, and I was then able to connect. It has worked flawlessly since.

[krone6]

The image is not found when I try to add murmur (mumble server). Any idea how to fix this?

[coppit]

How exactly are you trying to use the image? By clicking "add" under community applications? And you're using mine and not nativedude's?

[krone6]

How exactly are you trying to use the image? By clicking "add" under community applications? And you're using mine and not nativedude's?

 

Both the community applications and your repository along with nativedude's repository. It even does it on a docker I had installed and tried to reinstall it the same way with the same config. I restarted docker and then restarted the server with no luck. This started about a day or two ago if I had to guess as I was able to install dockers just fine up until now.

[Squid]

How exactly are you trying to use the image? By clicking "add" under community applications? And you're using mine and not nativedude's?

 

Both the community applications and your repository along with nativedude's repository. It even does it on a docker I had installed and tried to reinstall it the same way with the same config. I restarted docker and then restarted the server with no luck. This started about a day or two ago if I had to guess as I was able to install dockers just fine up until now.

Try maybe setting static DNS addresses under network settings (8.8.8.8 and 8.8.4.4 will work) and reboot to ensure they take effect and try it again.  If your ISP is anything like mine, their DNS servers suck.

[krone6]

How exactly are you trying to use the image? By clicking "add" under community applications? And you're using mine and not nativedude's?

 

Both the community applications and your repository along with nativedude's repository. It even does it on a docker I had installed and tried to reinstall it the same way with the same config. I restarted docker and then restarted the server with no luck. This started about a day or two ago if I had to guess as I was able to install dockers just fine up until now.

Try maybe setting static DNS addresses under network settings (8.8.8.8 and 8.8.4.4 will work) and reboot to ensure they take effect and try it again.

 

Already use those static DNS's. Anything else I could try?

[Squid]

How exactly are you trying to use the image? By clicking "add" under community applications? And you're using mine and not nativedude's?

 

Both the community applications and your repository along with nativedude's repository. It even does it on a docker I had installed and tried to reinstall it the same way with the same config. I restarted docker and then restarted the server with no luck. This started about a day or two ago if I had to guess as I was able to install dockers just fine up until now.

Try maybe setting static DNS addresses under network settings (8.8.8.8 and 8.8.4.4 will work) and reboot to ensure they take effect and try it again.

 

Already use those static DNS's. Anything else I could try?

The only other thing I can think of is another guy here had a similar problem with plugins, and the solution was to ultimately delete his /boot/config/network.cfg / reboot / reset the settings

 

[Squid]

Or your docker.img file is full and/or corrupted

[krone6]

Or your docker.img file is full and/or corrupted

 

None of those worked. I first made a new image and tried the above methods. I then deleted my network.cfg file and did a reboot and resetup a static ip and dns to 8.8.8.8, 8.8.4.4., 4.2.2.4 and still didn't have any luck.

 

Here is the code I am seeing:

 

root@localhost:# /usr/bin/docker run -d --name="MumbleServer" --net="bridge" -e TZ="America/New_York" -p 64738:64738/tcp -p 64738:64738/udp -v "/mnt/cache/Docker/":"/data":rw coppit/mumble-server
Unable to find image 'coppit/mumble-server:latest' locally
Pulling repository coppit/mumble-server
Get https://index.docker.io/v1/repositories/coppit/mumble-server/images: x509: failed to load system roots and no roots provided

 

By the way, is it fine if I issue a reboot from a telnet session while the array's running? I was under the assumption it stops everything gracefully before rebooting similar to windows shutting down however I am starting to think it's more of a hard reboot at this point.

[coppit]

Or your docker.img file is full and/or corrupted

 

Yeah, that's really annoying. I've been using this to clean up images: https://github.com/auser/yadr/blob/master/bin/docker-cleanup.sh

[exist2resist]

How do I set the SU password... does it work using docker exec?

[exist2resist]

I need to know where in the docker container the murmur.x86 file is located.

 

I can change the su password via docker exec.

docker exec MumbleServer ./murmur.x86 /data/mumble-server.ini -supw MyPassword

 

I need the exact location of the ./murmur.x86

[exist2resist]

Figured it out.

 

This is a debian based installation so murmur runs as a service, as per this site and instructions: http://wiki.mumble.info/wiki/Running_Murmur#Setting_the_SuperUser_Password

 

You can change your SU password for Murmur from bash on Unraid like so:

docker exec MumbleServer sudo -i murmurd -ini /data/mumble-server.ini -supw YourPassword

 

Cheers

[coppit]

Pardon the ignorance, but what's the benefit of running it that way versus "docker run"? The container already knows how to start the server, and you can always to "docker exec -it <container name> bash" later to attach to a running container.

[exist2resist]

You can run it from a script if you want. In the end setting the su password doesn't matter if you do it manually.

 

[Conson Droppa]

Also I am sorry for the ignorance but there is /data in the container volume field. Do I need to populate the Host path with a location.

 

Any folder?

Cache?

[dirtysanchez]

Also I am sorry for the ignorance but there is /data in the container volume field. Do I need to populate the Host path with a location.

 

Any folder?

Cache?

 

It needs to be mapped to the location the Mumble container will store it's data.  Same as any other docker (but usually called /config in other dockers).

 

For example /mnt/cache/appdata/mumble.

[Conson Droppa]

Did exactly that. Thanks!!!