https://registry.hub.docker.com/u/hurricane/tinymediamanager/

 

PS it might still be building.

Thanks a ton. Works great 

Is there a guide that explains how to install containers from the registry?  I have only used templates so far and I'm struggling.

 

Hurricane...I saw your instructions on the registry.  The thing that confused me was this:

 

Download latest TinyMediaManager from here.

Extract to a location such as /tmm on the host and ensure the directory and all files are by uid 99 and gid 100 (nobdy and users on unRAID).

 

I'm comfortable with the docker run commande but can you elaborate on the above?  How does this translate in the unRAID world?

 

TIA!

 

John

NM...got it working. 

 

Thx for making this!

 

John

I will create a template shortly. I'm also updating the image from supervisor to circus, because I would like the boot process of the container to be more fail safe.

Sounds like a plan.

 

How do you like TMM?  I have never sued it before.  Previously I have used MCM and MC.  How do you think this fairs?

 

John

Quick question...

 

Is there a trick to setting permissions on downloaded metadata?  When I scrape a movie, I cannot modify/delete the files that were downloaded (from my laptop...WIN7).

 

If I run New Permissions script, all is good and I can modify files.

 

John

Perhaps once I start using circus I can achieve this. In terms of tmm, I really like. It seems to be doing really well. I use it in conjunction with MediaBrowser.

FYI...found some weirdness.  Not with the container but with TMM itself:  http://forum.kodi.tv/showthread.php?tid=208933

 

John

Is this container working ?  I run TMM from my desktop but if I could trigger it via cron /command line running on my server that would be very cool

Yes you can. Are you running the docker version or just the actual java install?

 

If using docker with the new image https://registry.hub.docker.com/u/hurricane/tinymediamanager/

 

I would use docker exec -ti containername /scripts/tinyMediaManangerCMD.sh $PARMS

 

replace containername with the name of your container and replace $PARMS with available options, please tinyMediaManager readme or forum for this info.

How do i go about updating TMM. I see that a new version (2.6.5) has been released but there has been no notification on the docker so far.

Thanks in advance

I will update it shortly. Thanks for the post. If you wanted to do it manually docker exec would be the best, I will update the image though. unRAID best practice suggest all updating be done by developers and not the containers themselves.

I will update it shortly. Thanks for the post. If you wanted to do it manually docker exec would be the best, I will update the image though. unRAID best practice suggest all updating be done by developers and not the containers themselves.

 

Thank you

Just as an info, v2.6.6 is out introduces trakt.tv 2.0 API. 

Thanks. I will update it soon.

I just updated to the latest version and it looks like something has gone wrong with the update. Cant seem to connect to the server.

 

Failed to connect to server (code: 1006)

 

EDIT: tried reinstalling the docker and the same issue persists but in the install screen i got this...

 

IMAGE ID [53f858aaaf03]: Pulling metadata. Pulling fs layer. Downloading -6575530100% of -0MB. Download complete.
IMAGE ID [837339b91538]: Pulling metadata. Pulling fs layer. Downloading -7147900% of -0MB. Download complete.
IMAGE ID [615c102e2290]: Pulling metadata. Pulling fs layer. Downloading -68000% of -0MB. Download complete.
IMAGE ID [b39b81afc8ca]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [8254ff58b098]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [ec5f59360a64]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [2ce4ac388730]: Pulling metadata. Pulling fs layer. Downloading -1105000% of -0MB. Download complete.
IMAGE ID [2eccda511755]: Pulling metadata. Pulling fs layer. Downloading -3150900000% of -0MB. Download complete.
IMAGE ID [5a14c1498ff4]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.

 

Is this normal?

This might a docker error.  I will double check it, maybe I have to recreate the repository from scratch since I made some major overhaul.

 

Can you please retry again, and report back.

I just updated to the latest version and it looks like something has gone wrong with the update. Cant seem to connect to the server.

 

Failed to connect to server (code: 1006)

 

EDIT: tried reinstalling the docker and the same issue persists but in the install screen i got this...

 

IMAGE ID [53f858aaaf03]: Pulling metadata. Pulling fs layer. Downloading -6575530100% of -0MB. Download complete.
IMAGE ID [837339b91538]: Pulling metadata. Pulling fs layer. Downloading -7147900% of -0MB. Download complete.
IMAGE ID [615c102e2290]: Pulling metadata. Pulling fs layer. Downloading -68000% of -0MB. Download complete.
IMAGE ID [b39b81afc8ca]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [8254ff58b098]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [ec5f59360a64]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.
IMAGE ID [2ce4ac388730]: Pulling metadata. Pulling fs layer. Downloading -1105000% of -0MB. Download complete.
IMAGE ID [2eccda511755]: Pulling metadata. Pulling fs layer. Downloading -3150900000% of -0MB. Download complete.
IMAGE ID [5a14c1498ff4]: Pulling metadata. Pulling fs layer. Downloading -3200% of -0MB. Download complete.

 

Is this normal?

 

Thanks,

 

The pulling layers is fine. I discovered the issue. The problem is I change to using the phusion base image like everyone else, unfortunately I forgot that phusion uses trusty and that the x11vnc release in trusty hates it when you disable ipv6. unRAID by default doesn't have ipv6 enabled for docker and so x11vnc errors out with a buffer overrun. Anyhow I'm trying to resolve the issue while keeping the base image phusion. I promise you I tested the build before the release the problem is that I tested it on a ubuntu virtual desktop were ipv6 is not disabled. So when I release it I thought that issues like this weren't going to happen. My apologies. Just to give you heads up the container also support rdp now, so that another method you might be able to access once I get the issues resolved. Please reply rather than editing your message so that I may get notified. I will try and have this fix as soon as possible.

i'm trying to get a video conferencing server in a docker,  running and i'm hitting this ipv6 issue too.

 

 

I know, luckily I remember what the issue was. I'm not sure why it only does it in unraid. My ubuntu machine only has ipv4 and the same error doesn't pop up. Maybe it's the way docker is compiled for unraid?

I know, luckily I remember what the issue was. I'm not sure why it only does it in unraid. My ubuntu machine only has ipv4 and the same error doesn't pop up.

 

 

i can run the docker in my docker server VM and it works nicely and i can videochat to myself thus far, lol.

 

soon as i try it on my unraid box and it spits out some random errors specific to the app which google says is ipv6 related.

I know, luckily I remember what the issue was. I'm not sure why it only does it in unraid. My ubuntu machine only has ipv4 and the same error doesn't pop up. Maybe it's the way docker is compiled for unraid?

 

have to ask what the dependencies and configure was i guess ?

We should really get to the bottom of this because it makes no sense not to have certain images work in unRAID while they work on almost every other issue. Could it be that the kernel in unRAID is not compiled with ipv6?

Just checked the kerneel config and IPV6 is not set. Wonder if that's the issue.