This is a barebones docker container built using busybox and a statically compiled version of murmurd from the official website.
It's configured to look for the configuration file in
The recommended way to run this container is as follows:
$ docker run -d -p 64738:64738 -p 64738:64738/udp mattikus/murmur
To have the container store the sqlite database on your filesystem instead, you can run:
$ docker run -d -p 64738:64738 -p 64738:64738/udp \ -v /path/to/data:/data mattikus/murmur
Getting the super-user password
On first run, if you don't already have an existing state database, you'll want to look at the logs for your container to get the super-user password:
$ docker logs murmur 2>&1 | grep Password <W>2014-07-27 01:41:31.256 1 => Password for 'SuperUser' set to '(mAq3hkwnkD'
Providing your own murmur.ini
If you want to tweak the provided murmur.ini, you should run:
docker cp your-container-name:/etc/murmur.ini /path/to/murmur.ini
If you are using the built in volume at
/data/, then you should sure your config contains:
To run the container with your tweaked murmur.ini:
$ docker run -d -p 64738:64738 -p 64738:64738/udp \ -v /path/to/murmur.ini:/etc/murmur.ini mattikus/murmur
Very handy, I'm using the following script whenever I create a container using this image (only requires my murmur.ini file to be present in working directory), it sets up everything (including changing password)
docker pull mattikus/murmur
docker volume create $VOLUMENAME
docker run -d -p 64738:64738 -p 64738:64738/udp -v $VOLUMENAME:/data -v $(pwd)/murmur.ini:/etc/murmur.ini --name=$CONTAINERNAME $RESTARTPOLICY mattikus/murmur
echo "Giving Murmur a few secds to start..."
echo "Changing Superuser password to $PASSWD"
docker exec -it $CONTAINERNAME /opt/murmur/murmur.x86 -v -supw $PASSWD
Actually, it looks like it's a normal 32bit static intel build. For alternate architectures you'd need to use another docker container that builds from scratch.
It's probably because this is a x86_64bit binary and you might be running it on a 32bit or alternate architecture.
I'll make that more clear in the description, thanks for letting me know.
When I try to run this with docker 1.0.0, it exits immediately with this in the logs:
2014/08/17 11:57:46 exec format error