I think I was able to get started using Madsonic via this command:

 

docker run -d -h unraid --name="madsonic" -v /mnt/user:/mnt -v /mnt/cache/docker/apps/appdata/madsonic/:/config -v /etc/localtime:/etc/localtime:ro -p 4040:4040 -p 443:443 botez/docker-madsonic

 

Which is pulling from here: https://registry.hub.docker.com/u/botez/docker-madsonic/

 

I didn't have time to set anything up other than a password but I was able to get to the website (no https/443 yet though).

 

EDIT 20141013: I changed the title of the OP because this, while being a fork of Subsonic, is not a subsonic container. To avoid confusion this thread just talks about Madsonic. Not only that but they're not my containers! So if you don't get the support you'd think you should I'm sorry but I posted this back in the early days of docker support on unraid. It was like the wild west back then.

That's my docker, so let me know if you run into any issues with it.

 

Sent from my VS980 4G using Tapatalk

 

 

Awesome, did you already post it here? I was searching around but perhaps I missed it. So far it looks like there's no transcoders installed but I haven't really gotten into it at all other than adding a library and a user.

No -- I haven't posted it here yet due to the transcoder issue which I was working on yesterday.  I just fixed that a few minutes ago, so now the latest x64 transcoders should be installed to your /config/transcode folder.  I also updated to the latest beta build.

Awesome! Now I just need to figure out how to update a container

docker rm -f <container_name>

docker rmi botez/docker-madsonic

docker run ...

I just updated the docker to the latest Madsonic beta release. 

I had to update your Dockerfile with the July 20 standalone zip because I was getting an error others were seeing on the madsonic forums. I basically just changed some commented out stuff you had for update:

 

# install update
ADD http://madsonic.org/download/5.1/20140721_madsonic-5.1.4820.beta2-standalone.zip /usr/share/madsonic/update.zip
RUN cd /usr/share/madsonic && unzip -o update.zip
RUN chmod +x /usr/share/madsonic/*

 

Source: http://forum.madsonic.org/viewtopic.php?f=34&t=1134&p=3625&hilit=XmlBeanDefinitionStoreException&sid=0b497825378b93a797e0080487bff467

What issue were you exactly seeing?  I've been using this build for a while without issues.

Specifically the one seen by this user: http://forum.madsonic.org/viewtopic.php?f=34&t=1134&p=3625&hilit=XmlBeanDefinitionStoreException&sid=d7e956566eb03cfd4a11bbecac308ba9#p3625

hi all, installed this and (with a little help from botez) all is running great.

one thing i noticed was, it seems extremely slow on a folder scan. while it used to take about 2 to 3hrs when i had subsonic installed as an plugin-app, as docker install a full folder scan takes at the moment over 10hrs!!!!

did anybody else experience a massive slowdown on folder scan as well? since everything else seems to work as fast/ slow as before that's still a big surprise for me!

 

cheers, L

hmm, anybody? with any experience either way?? i can't be the only madsonic user in the whole unraid universe!

 

cheers, L

Nothing that I've noticed but my library isn't huge and it scans at like 3am

im running madsonic in a docker container and it works fine, i have a 200GB music collection and madsonic can scan it in around 20 mins. the docker im using is my own creation, you are wlecome to give it a whirl if you want, its running the latest stable version of madsonic (not tech demo releases).

 

https://registry.hub.docker.com/u/binhex/arch-madsonic/

 

its arch linux based not phusion as this is my preferred platform.

I got a bunch of errors related around transcoding last time I tried yours and it seems I still do

 

2014-08-01 23:52:51,966 CRIT Set uid to user 0
2014-08-01 23:52:51,967 WARN Included extra file "/etc/supervisor/conf.d/madsonic.conf" during parsing
2014-08-01 23:52:51,973 INFO supervisord started with pid 1
2014-08-01 23:52:52,976 INFO spawned: 'transcode' with pid 8
2014-08-01 23:52:52,978 INFO spawned: 'madsonic' with pid 9
2014-08-01 23:52:52,996 DEBG 'transcode' stderr output:
cp: cannot stat ‘/tmp/linux/*’: No such file or directory

2014-08-01 23:52:53,002 DEBG 'transcode' stderr output:
chmod: cannot access ‘/config/transcode/*’: No such file or directory

2014-08-01 23:52:53,002 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47866243421968 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stdout)>
2014-08-01 23:52:53,002 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47866243422328 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stderr)>
2014-08-01 23:52:53,002 INFO exited: transcode (exit status 1; not expected)
2014-08-01 23:52:53,003 DEBG received SIGCLD indicating a child quit
2014-08-01 23:52:54,006 INFO spawned: 'transcode' with pid 37
2014-08-01 23:52:54,006 INFO success: madsonic entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2014-08-01 23:52:54,019 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47866243422328 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stdout)>
2014-08-01 23:52:54,020 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47866243422256 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stderr)>
2014-08-01 23:52:54,020 INFO exited: transcode (exit status 0; not expected)
2014-08-01 23:52:54,020 DEBG received SIGCLD indicating a child quit
2014-08-01 23:52:56,024 INFO spawned: 'transcode' with pid 38
2014-08-01 23:52:56,038 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47866243422256 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stdout)>
2014-08-01 23:52:56,038 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47866243421968 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stderr)>
2014-08-01 23:52:56,038 INFO exited: transcode (exit status 0; not expected)
2014-08-01 23:52:56,038 DEBG received SIGCLD indicating a child quit
2014-08-01 23:52:59,043 INFO spawned: 'transcode' with pid 41
2014-08-01 23:52:59,057 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47866243421968 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stdout)>
2014-08-01 23:52:59,057 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47866243422616 for <Subprocess at 47866243421896 with name transcode in state STARTING> (stderr)>
2014-08-01 23:52:59,057 INFO exited: transcode (exit status 0; not expected)
2014-08-01 23:52:59,058 DEBG received SIGCLD indicating a child quit
2014-08-01 23:53:00,059 INFO gave up: transcode entered FATAL state, too many start retries too quickly

Hi pinion I spotted the bug, can you delete container and image and pull again, should run with zero errors.

Still seeing a lot of the same errors after removing the container and the image and starting over.

2014-08-04 22:12:51,282 CRIT Set uid to user 0
2014-08-04 22:12:51,283 WARN Included extra file "/etc/supervisor/conf.d/madsonic.conf" during parsing
2014-08-04 22:12:51,289 INFO supervisord started with pid 1
2014-08-04 22:12:52,292 INFO spawned: 'transcode' with pid 8
2014-08-04 22:12:52,294 INFO spawned: 'madsonic' with pid 9
2014-08-04 22:12:52,306 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47905873745680 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stdout)>
2014-08-04 22:12:52,306 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47905873746040 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stderr)>
2014-08-04 22:12:52,306 INFO exited: transcode (exit status 0; not expected)
2014-08-04 22:12:52,306 DEBG received SIGCLD indicating a child quit
2014-08-04 22:12:53,309 INFO spawned: 'transcode' with pid 33
2014-08-04 22:12:53,310 INFO success: madsonic entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2014-08-04 22:12:53,324 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47905873746040 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stdout)>
2014-08-04 22:12:53,324 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47905873745968 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stderr)>
2014-08-04 22:12:53,324 INFO exited: transcode (exit status 0; not expected)
2014-08-04 22:12:53,325 DEBG received SIGCLD indicating a child quit
2014-08-04 22:12:55,329 INFO spawned: 'transcode' with pid 34
2014-08-04 22:12:55,342 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47905873745968 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stdout)>
2014-08-04 22:12:55,342 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47905873745680 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stderr)>
2014-08-04 22:12:55,343 INFO exited: transcode (exit status 0; not expected)
2014-08-04 22:12:55,343 DEBG received SIGCLD indicating a child quit
2014-08-04 22:12:58,348 INFO spawned: 'transcode' with pid 37
2014-08-04 22:12:58,362 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47905873745680 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stdout)>
2014-08-04 22:12:58,362 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47905873746328 for <Subprocess at 47905873745608 with name transcode in state STARTING> (stderr)>
2014-08-04 22:12:58,362 INFO exited: transcode (exit status 0; not expected)
2014-08-04 22:12:58,362 DEBG received SIGCLD indicating a child quit
2014-08-04 22:12:59,364 INFO gave up: transcode entered FATAL state, too many start retries too quickly

grr ok pinion i got it sorted, supervisor was attempting to restart the transcode script due to it starting and stopping too quickly and thus the errors in the log, give it another go, you will of course need to delete container and image.

grr ok pinion i got it sorted, supervisor was attempting to restart the transcode script due to it starting and stopping too quickly and thus the errors in the log, give it another go, you will of course need to delete container and image.

 

If you are running a script once with supervisor, you should set "startsecs" to 0 and disable the autorestart.

grr ok pinion i got it sorted, supervisor was attempting to restart the transcode script due to it starting and stopping too quickly and thus the errors in the log, give it another go, you will of course need to delete container and image.

 

If you are running a script once with supervisor, you should set "startsecs" to 0 and disable the autorestart.

 

yes that was my final solution  , was confusing me for a little while as i was getting exit code 0 not expected (when actually 0 is expected) but it was still restarting, obviously my little script was starting and stopping too quickly and thus supervisor thought it was a failed start, you live and learn 

grr ok pinion i got it sorted, supervisor was attempting to restart the transcode script due to it starting and stopping too quickly and thus the errors in the log, give it another go, you will of course need to delete container and image.

 

 

2014-08-05 22:30:19,890 CRIT Set uid to user 0
2014-08-05 22:30:19,890 WARN Included extra file "/etc/supervisor/conf.d/madsonic.conf" during parsing
2014-08-05 22:30:19,896 INFO supervisord started with pid 1
2014-08-05 22:30:20,898 INFO spawned: 'transcode' with pid 8
2014-08-05 22:30:20,900 INFO spawned: 'madsonic' with pid 9
2014-08-05 22:30:20,912 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47955731040088 for <Subprocess at 47955731040016 with name transcode in state STARTING> (stdout)>
2014-08-05 22:30:20,912 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47955731040448 for <Subprocess at 47955731040016 with name transcode in state STARTING> (stderr)>
2014-08-05 22:30:20,912 INFO success: transcode entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2014-08-05 22:30:20,912 INFO exited: transcode (exit status 0; expected)
2014-08-05 22:30:20,912 DEBG received SIGCLD indicating a child quit
2014-08-05 22:30:21,914 INFO success: madsonic entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Yep that's a successful start :-)

im running madsonic in a docker container and it works fine, i have a 200GB music collection and madsonic can scan it in around 20 mins. the docker im using is my own creation, you are wlecome to give it a whirl if you want, its running the latest stable version of madsonic (not tech demo releases).

 

https://registry.hub.docker.com/u/binhex/arch-madsonic/

 

its arch linux based not phusion as this is my preferred platform.

yeah well, i am looking more at about 11+ tb in music. so generally i am used to longer scans. and everything with botez madsonic-docker works fine + awesome help from him for the few issues i had.

not trying to say you didn't do an equally awesome job, i just try to stick with one 'edition' right now. unfortunately i have no spare server sitting around at this point to play. since i am not 100% firm with the whole docker story yet, i am kinda cautious about installing two diff. versions on my system.

anyway, i am aware that i have a rather large music collection. i am also fine with the idea that it takes just a little extra time to scan. i was just wondering about the absurd long full scan time (where the system itself does not to be challenged at all). as soon as my have my sandbox server back up, i will give your docker version a shot as well. till than i stick with the working one (i am sure you understand that).

i was wondering if it may have to do with the underlaying OS, but as i said - my hardware is far away from being challenged.... so i dont know.

hi lars, firstly no biggie if you decide not to use my docker, the dockers listed in my docker repo are created for myself firstly, so all of the ones listed there are actively used and updated by myself, so i will leave it up to you if you want to try it out.

 

as far as testing two installations of madsonic on the same server this is VERY doable and one of the really cool things about dockers, all you need to do is specify a different port on the host side (left hand port number) to your other madsonic docker and preferably a different config folder to store your database and config files in, then just run and give it a go, if it doesnt work then simply stop, rm container and then rmi images.

 

and lastly, wow 11 TB of music, i dont want to know how long thats took you to collect!!!!! 

Just to chime in, I'm actually running both right now. It's not running two different versions of docker although they do have different base images but that doesn't matter. I'm mapping botez's container to ports 4040 and binhex's to 4041 and 4051 (although I'm only using 4051 and running it over https). The advantage here is I can have the stable version from binhex (plus https and I can have the bleeding edge with botez's. It's pretty awesome really. Heck, you could spin up a dozen containers of madsonic and have a madsonic app for each genre of music you have. Well, that might take more than a dozen but you get my point. I'm actually considering doing this anyway so I can have a separate container just for my collection of live bootlegs since they don't typically have good tags or cover art and you can't just scan a database on the internet to fill it in. And I prefer not to share them along with the rest of my music.