More > JRiver Media Center 25 for Linux

Docker image with MC25

<< < (9/9)

max096:
Restarting docker or the entire PC sometimes helps with weird docker problems.
I dont think your theory is right since jatzoo's image does work for me (I'm not actually using it, I just tried if it works yesterday). But I don't know right now how to possibly remote troubleshoot that.

You could try to "docker rm -f <your_container>", then "docker image prune" to remove un-used images. Then try "docker run" again. Could be that the image somehow currupted on your PC. Although, I have never encountered it.

Either way the apt installation in jatzoos image is not broken and the image was never changed or updated since it was uploaded, since the way it updates is with apt inside the container. I can confirm is working as of yesterday.

-------------------------------------

But

https://hub.docker.com/r/shiomax/jrivermc25

You could try this one.

For that create a new directory "config" then move your current directory into that directory and name it ".jriver". (As always better first backup your current directory).

Then you can use this run command


--- Code: ---docker run -d \
    --name=jrivermc25 \
    --net=host \
    --restart=always \
    -v config:/config:rw \
    -v /path/to/music:/data/music:rw \
    -e VNC_PASSWORD=12345 \
    shiomax/jrivermc25

--- End code ---

You should also replace "/data/music" with the path where you stored your music in the other container in the other image and the "path/to/music" with your music directory on the host. For the config directory this command assumes you are running the command from the directory where the config directory is located on your disk. If you run it from anywhere else you can, but you will have to provide the full path to it then.

This image never should have problems with apt, since it does not have apt installed and does not update at runtime. Updates are handled entirely at build time and its currently automatically rebuilding every Sunday. If a new image that was built causes problems you can use one of the previously built image. You can find more information about that in the readme.

To update that image with the docker commands. You can run these three commands (replace the last command with whatever you ran before when initially creating the container)


--- Code: ---docker pull shiomax/jrivermc25:latest

docker rm -f jrivermc25

docker run -d \
    --name=jrivermc25 \
    --net=host \
    --restart=always \
    -v config:/config:rw \
    -v /path/to/music:/data/music:rw \
    -e VNC_PASSWORD=12345 \
    shiomax/jrivermc25

--- End code ---

Or you use compose as suggested in the readme. Then you don't have to keep track of the run command somehow.

ajw1997:
Hello,
After much digging, it seems that the problem with how my QNAP NAS accesses the internet.
It was not able to update the virus definitions, and other issues.
Anyway, I found a post about this problem, with the advice to change the DNS settings to 8.8.8.8 and 8.8.4.4.
https://forum.qnap.com/viewtopic.php?f=25&t=144837
And it now all works again fine.
I'm not sure what the problem was-may have been from a QNAP OS update.  Anyway it now works.
Thanks for trying to help. 
Bizarre.
Regards,
Andrew

Grundgütigster:

In my next life I will become a computer expert and be able to install the docker version of MC on my QNAP NAS.

Navigation

[0] Message Index

[*] Previous page