[How To] Update ioBroker js-controller in Portainer

[gyroslav]

hello world,
here a small HowTo update your iobroker in docker through portainer:

1. i assume, you have portainer running

2. navigate to your running iobroker-container and click "console"
   

3. click CONNECT

4. to stop the iobroker daemon:
   pkill -u iobroker
   google on how to stop iobroker will give you mostly "pkill io" and this will close the terminal und restart iobroker.
   so the flag "-u" is very importand here.

5. from here you can follow the official instructions:
   iobroker update
iobroker upgrade self
iobroker start

6. restart the container

[fzzybllz]

Hi @gyroslav,

very nice idea, but unfortunately your how to is old and i guess deprecated, isn't it @buanet?

Steps 1 to 3 are still ok, but step 4 is fixed by the maintenance script. So step 4 has to be maintenance on -> confirm with yes
Step 5 is partially fine, but instead of iobroker start you have to switch the maintenance script off by maintenance off + confirmation.
Step 6 will be performed automatically by the maintenance script

[gyroslav]

Actually the official instructions you get, after clicking on the Update-Button located here:

are:

iobroker stop
iobroker update
iobroker upgrade self
iobroker start

i cannot show it right now, because it is allready done :)

[fzzybllz]

That's right, but it's meant to be for a plain installation of iobroker without docker. Iobroker does not detect, if it's running in docker or directly on the OS.

[gyroslav]

OK next time there is an update, I will look for the "maintenance on" instructions. And change my howto above.

[McTristan]

I'm quite a bit confused of how the iobroker docker image update seems to work when persisting the volume information - not at all it seems as the mapped volume contains the whole iobroker installation.

It seems I'm running V5 of iobroker at the moment (even though I'm running the latest image which is V6 based).

With the above described method I can at least update to v5.2.3 but what would I need to get the latest version 6?

Or would it be wise to ditch the mapped volume, start from scratch und restore from a backup?

Or is there an "easy" way to upgrade to v6?

[gyroslav]

Thats weird, i get only the Versions 3.3.22

I will use this instruction for my next update: https://smarthome.buanet.de/2020/10/iobroker-docker-container-updates-upgrades/

[McTristan]

Actually I meant the iobroker version and not the JS Controller version. As the newest Docker image is based on v6.x I was wondering how to archive the same when using a volume map as suggested by the maintainer. When I update the container either by using the above mentioned method (using the iobroker commandline tools) or by using the newest image (I'm using portainer to update my containers) I always end up with a v5 version of iobroker.
So either I'm doing something wrong or there must be another way of doing this...

[buanet]

I always end up with a v5 version of iobroker.

How do you check the version of your ioBroker Docker container?

Attention: The version of the Docker Image has nothing to do with any version of the ioBroker components like adapters or js-controller! Also the labels of a container, as you can see them in Portainer, may not be updated when doing a recreate with pulling the image by latest tag.
The best place to find the version of the image you are running is checking the Log on container startup.

Regards,
André

[McTristan]

Actually I was wondering that too, now you are mentioning it. I thought the image versioning is based on the admins module main version.
Why would it be a version 6 if there is no iobroker version 6?

[buanet]

You were wrong.
There is no connection between the admin adapter and the ioBroker Docker image. So why should the versions match???

Just for clarification: ioBroker Docker image is NOT ioBroker. It is just an environment to run ioBroker. You can compare this a little to an operating system. The os brings everything you need to run ioBroker. The only connection between ioBroker software and the ioBroker Docker image is, that ioBroker is already preinstalled wenn you start it the first time. Like some apps are already preinstalled when you install Windows...

Regards,
André

[McTristan]

but the question remains: do I have to update iobroker always via a shell into the docker container?

[buanet]

Yes, like described in the docs: https://docs.buanet.de/iobroker-docker-image/docs/#updates-upgrades

[buanet]

@gyroslav Although it is a little outdated the update should work this way. I just changed the title and moved this to general discussions.
I will go for adding this to the official docs. Thank you.

Regards,
André

[TZanke]

Has anyone tested the new maintenance script as a replacement for the solution described by @gyroslav ?

https://docs.buanet.de/iobroker-docker-image/docs/#use-maintenance-script-beta

I do not have any pending update at the moment, so I hopefully will find this comment next time I open the bookmark to this How To if I need to.

Edit:
works!

Code:

maintenance on 
iobroker update
iobroker upgrade self
maintenance restart

Edit2:
see: https://docs.buanet.de/iobroker-docker-image/docs/#updates-upgrades

Code:

maintenance upgrade

[McR1983]

Hey,

teste gerade dein 9Beta-Node20.
Funktioniert jetzt soweit, aber der Script Maintenance lässt sich nicht ausführen da der user falsch wäre. Welcher ist richtig?

[buanet]

Steht aber eigentlich in der Meldung:

MfG,
André

[McR1983]

Ich würde das mit einem Iobroker User also Admin oder einem im Iobroker zusätzlich hinzugefügen user Interpretieren.. was aber nicht funktionierte im portainer...

[McR1983]

ok es ist "iobroker" gemeint.
Anführungszeichen wären gut lol