Linux Docker v2.1 upgrade problem
|
17-12-2021, 16:51
Post: #1
|
|||
|
|||
Linux Docker v2.1 upgrade problem
I have been running MinimServer 2.0.18 in Linux Docker for a while with no problems. I have however just upgraded to v2.1and the installation seems to have gone OK. I can access the local MinimServer web page to update my license information, profile etc. I have installed the new version of MinimWatch on my Win10 PC which seems to be running OK.
The problem however is that my MinimWatch installation cannot 'see' the new Docker installation at all despite having the 'ohnet.subnet' set to 192.168.86.0 which is correct for my one and only home network. Thus I cannot check/correct any of the MinimServer properties via this route. The MinimWatch log records no errors when connecting to the new Docker installation. Can anybody help with this problem please ? Thanks Chris |
|||
17-12-2021, 22:03
Post: #2
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
Did you set the network type to Host when you created the Docker container? If you didn't do this, your Docker instance of MinimServer will not be visible to other devices on your network.
|
|||
18-12-2021, 11:10
Post: #3
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
Simon
Thanks for this pointer, it was the cause of my problem. However in trying to resolve this issue I have used up all 3 of my full licenses. It is very easy to forget to deactivate the license when killing a Docker container (must be my age). Can you please delete all 3 of the current licenses I hold under name 'ceejayemm@hotmail.com' so that I can now license this (hopefully) working version. Is there any chance that users will get the ability to manage their own license records so that, as in this case, a forgetful moment can be rectified without needing to bother you ? Thanks as always for you very helpful support. Chris |
|||
18-12-2021, 12:39
Post: #4
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
I have deactivated one of these (the most recent). I am not able to do any more work on this today. Doing a forced deactivation can be tricky depending on the state of the license database. This is why it is not available as a user facility.
|
|||
20-12-2021, 10:12
Post: #5
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
Simon
Much appreciated, I am back to a fully licensed, working system. Please remove the remaining 2 licenses (Linux, dated 16 Dec 2021 and 17 Dec 2021) as and when you can. Thanks Chris |
|||
26-01-2022, 10:14
(This post was last modified: 26-01-2022 10:15 by ceejayemm.)
Post: #6
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
Simon
I have done it again. I read here: https://forum.minimserver.com/showthread...8#pid43308 That, as I am already running v2.*, I don't need to uninstall to upgrade to v2.1. Does this apply to a Docker installation ? Where does the configuration information persist in a Linux based Docker installation as there are no instructions where this might be - or have I missed it ? With hindsight, the Music library volume will persist from one install to another but there doesn't seem to be an associated volume for the configuration information to persist. I redeployed my existing Docker container (through Portainer) to get the latest version but though it seems to have installed the new version I can no longer install MinimStreamer as it appears this updated installation has reverted to the Starter License and I can no longer activate the full license I have as all my license slots are taken up (by old versions on now none existent docker instances): [3c2c489e] All 3 activations for this license are being used by other devices I note your comments above about the problems regarding providing a licence management facility but I think you perhaps need to rethink this. In the meantime if you can find a few minutes to clear out the licenses held on my account I would appreciate it. Regards. Chris |
|||
26-01-2022, 13:47
Post: #7
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
The discussion in the other thread was about running MinimServer on Synology DSM. You are running MinimServer in a Docker container that is not hosted on Synology.
A Docker container hosted on Synology or QNAP can be updated to a new MinimServer version without losing the license activation. For a Docker container hosted on other systems, you need to deactivate the MinimServer full license before destroying the container. This applies to all Docker containers, including when you are creating a new Docker container with the same MinimServer version and when you are creating a new Docker container with a new MinimServer version. From your earlier post, it appears you installed MinimServer 2.1 in a Docker container on 17 December. In your latest post, you said you had redeployed the Docker container to get the latest version. The latest version is still 2.1 so I am not sure why you did this. There have been updates released since 17 December but these are automatically applied to your existing 2.1 container. The only reason you would need to redeploy the container is for a new version 2.x or 2.1.x. I have deactivated all 3 of your license activations. It appears that I did not remember to deactivate the other 2 activations in December. My apologies for this. A lot was happening then. |
|||
26-01-2022, 21:04
Post: #8
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
Simon
Thanks for the quick turn around on this issue. I am up and running again. In my haste to look for a solution to my problem I missed out a vital bit of info. Yes, as you noted, I did upgrade to v2.1 back in November which eventually worked. The info I missed was that in early January I have to move my music library to a new location and in order to to make the necessary change to MinimServer I had to update the Docker volume setting and this necessitated redeploying the image to a new container. in my rush to do this, thinking I WASN'T upgrading I forgot to deactivate the license before redeploying the image. I still think it would be worthwhile considering setting up a new persistent volume for the configuration/license data for Linux Docker installations. Many thanks again for the swift response. Chris |
|||
27-01-2022, 10:23
(This post was last modified: 27-01-2022 10:24 by simoncn.)
Post: #9
|
|||
|
|||
RE: Linux Docker v2.1 upgrade problem
(26-01-2022 21:04)ceejayemm Wrote: I still think it would be worthwhile considering setting up a new persistent volume for the configuration/license data for Linux Docker installations. This wouldn't solve the problem because the configuration/license data contains information derived from internal properties of the container that activated the license. Attempting to reuse this in a different container would result in a validation error. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)