More > JRiver Media Center 25 for Linux
JRiver MC25 Docker Image with WebUI as VNC
BryanC:
--- Quote from: max096 on June 17, 2019, 05:23:08 pm ---
--- Code: ---MC uses inotify to update automatically when files are on a local filesystem.
inotify doesn't work for cifs so the fallback is to the timed auto-checking on cifs mounted filesystems. There may be other filesystems that don't work for inotify either.
Note that the auto-import can be triggered from JRemote (iOS, not sure about android).
Also since it's a MCWS command you could make a curl string to the localhost:52199 MC library server to do the same as well.
--- End code ---
I don't use CIFS mount (on my main jriver instance anyways), since the mdadm raid6 formatted with etx4 is local to the system running the container. But I did volume mount it into the docker container. All I can say is that it does not work instantly for me now (and never did, since I was using docker) and it most likely will be consistently the same with any filesystem and mount option you use, since at the end of the day you are always gonna have to use docker volume mounts to map your music, or you don't have your music inside the container.
As I said I didn't even really start doing that. That's something that will appear in the dev-tags, whenever I find time to do so. But if it works out perfectly, I'll probably be putting that into the stable and latest tags to as an option to use.
I don't really wanna be using curl, because it might be needing logins (and seems unnecessarily) and there appear to be MC core commands available for triggering autoimport from the CLI.
Another option would be to forgo auto-import entirely and use the import methods instead. But that would also mean I'd have to do the delete and all those "fixing broken links" things when files change. Just run auto import seems a h3ll of a lot simpler. Although, you'd have 2 auto import triggers running at the same time then. Witch isn't perfect either. Though ditching auto import would mean, you would not even have to configure it at all. You just tell it /data (for example) is where my music is. Mount 10 directories under /data/music1 /data/music2 and it just kinda would go ahead and do that, without auto import ever being a thing.
---
OR... you update JRiver to work well with docker volume mounts and I don't try anything... ^^
--- End quote ---
Have you tried a bind mount?
max096:
--- Quote ---Have you tried a bind mount?
--- End quote ---
https://docs.docker.com/storage/bind-mounts/
Afaik, bind mount is volume mount --volume -v as in volume mount. That's what the flags stand for.
BryanC:
Well then it should work as long as you have inotify-tools installed.
It looks like your base image doesn't include inotify-tools OOTB, have you installed them as part of your MC installation?
max096:
--- Quote from: BryanC on June 17, 2019, 06:36:32 pm ---Well then it should work as long as you have inotify-tools installed.
It looks like your base image doesn't include inotify-tools OOTB, have you installed them as part of your MC installation?
--- End quote ---
I have not explicitly installed them. Unless it does install with the repo/apk, I didn't. I'll see what happens when I install them them then.
EDIT:
I installed 'inotify-tools' in the dev images now. Gonna test that tomorrow as it's kinda late now for me and i gotta sleep at some point. I'm gonna reply tomorrow wether that worked or not. It also was a problem before with the JRiver container build by jatzoo for jriver24 for me. So I'm not sure if it's gonna solve it. But i'll test it and see. Before with that river24 mage it sometimes worked instantly, but it seemed to be a pure luck kinda thing and not consistent at all. Sometimes you sit around for a minute and wait.
BryanC:
Source for that info: https://stackoverflow.com/a/46804953
It doesn't make sense to me that MC wouldn't just rely on the kernel inotify, but I'm not a Docker guy and Stackoverflow says you need the tools, so there you go.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version