More > JRiver Media Center 25 for Linux
Docker image with MC25
ajw1997:
Hello,
The problem of JRiver freezing when I manually add new folders seems to have resolved itself.
I had set it to automatically import new folders. When it also froze.
But when I came back later to use JRiver it seems to have imported new folders.
And the 'manually add new folders' seems to be working again.
Bizarre!
Regards,
Andrew
max096:
--- Quote from: ajw1997 on July 29, 2019, 05:20:38 pm ---Hello,
The problem of JRiver freezing when I manually add new folders seems to have resolved itself.
I had set it to automatically import new folders. When it also froze.
But when I came back later to use JRiver it seems to have imported new folders.
And the 'manually add new folders' seems to be working again.
Bizarre!
Regards,
Andrew
--- End quote ---
Thats good then. Maybe you restarted the NAS or the 'container station' thing? Ive had docker die inside a few times already immidiately after an upgrade of docker itself. Restarting the service always fixed it again. But I dont know how to do that on what you are using. Restarting the entier system is the surefire way to achieve that though. Guess it just does not like it being replaced while its running.
Should add that to my list of remembering people to ask if they tried 'turning it off and on again'. It sounds kinda crishy, but it just works so often. ;)
ajw1997:
Hello,
After using Jriver25 with docker for a month or so, it is now not installing.
When trying to run it I get the message:
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
My reading of Google search results is that the 'image' needs to be revised to install the relevant package.
Is that correct?
If yes, how is this done?
Regards,
Andrew
max096:
--- Quote from: ajw1997 on August 09, 2019, 05:49:28 pm ---Hello,
After using Jriver25 with docker for a month or so, it is now not installing.
When trying to run it I get the message:
E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?
My reading of Google search results is that the 'image' needs to be revised to install the relevant package.
Is that correct?
If yes, how is this done?
Regards,
Andrew
--- End quote ---
What does it say when you run the image without the -d option or look into "docker logs image_name_or_id" when it "runs".
The image should not need any rebuilding to work.
Have you tried removing the container and recreating it? Or does it work when you create a new container entirely from scratch?
You could always "docker exec -it <container_name> /bin/bash" and then "apt intall apt-transport-https" (as a test if it works then), but normally it should not be needed. It works without that package. apt-transport-https was never installed in that image.
ajw1997:
Hello,
Thanks for your response. This asks great questions.
Before I respond, here is a copy of the log from the file "*-json.log"
{"log":"\r\r0% [Working]\r \rE: The method driver /usr/lib/apt/methods/https could not be found.\r\n","stream":"stdout","time":"2019-08-10T23:04:50.849676925Z"}
{"log":"N: Is the package apt-transport-https installed?\r\n","stream":"stdout","time":"2019-08-10T23:04:50.84982343Z"}
I respond to your questions below.
Q1. What does it say when you run the image without the -d option or look into "docker logs image_name_or_id" when it "runs".
The image should not need any rebuilding to work.
Answer:
I can see no "-d" option. I installed the docker using the Jatzoo instructions for JRiver 24.
Where would the "docker logs image_name_or_id" be?
Q2. Have you tried removing the container and recreating it? Or does it work when you create a new container entirely from scratch?
Answer: I have tried that multiple times, but as mentioned, using the Jatzoo instructions.
Q3. You could always "docker exec -it <container_name> /bin/bash" and then "apt intall apt-transport-https" (as a test if it works then), but normally it should not be needed. It works without that package. apt-transport-https was never installed in that image.
Answer: As the container does not actually run, I don't believe this is possible.
My Theory
Based on this post https://stackoverflow.com/questions/55834331/docker-image-rabbitmq-apt-broke, could it be that the container is trying to install/download a no longer maintained Linux respository?
If this is the case, the image may need to be updated.
Regards,
Andrew
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version