Updates

[Morningstar2808]

Hello. I understand that the mechanism for updating containers/images has not been fully implemented?
I tried updating arcane and arcane-agent from the panel—the update was successful, but in the case of arcane, the version did not change, and it still requires updates.
As for arcane-agent, it also updated, but now the panel shows that the latest version of images is not being used.

[Morningstar2808]

If you perform an update on the server using docker compose pull && docker compose down && docker compose up -d && docker, everything works fine and is displayed correctly in the panel.

[Morningstar2808]

If you connect to the server and start viewing the docker container logs, you can see that restarting the container from the panel works, but pulling images does not.

[kmendell]

Updating Arcane it self using the interface may not work, and its disabled via auto update as it wouldnt be able to complete the task sincei ts restarting it self.

[Morningstar2808]

I didn't quite understand🤔 I wrote that I can't update the docker container and image using the arcane panel, not only arcane-agent, but also other containers too. I don't use automatic container updates.

[wesuru]

Having the exact same issue. The actual Arcane updater doesn't seem to work (lower left hand corner where it states "update available - update to x.xx.x")

then once "updated"

....but then... ?

I did notice this in the logs, but ...nothing in my environment has changed, so unsure.

Yes I did notice that the available update went from 1.10.0 to 1.10.1 but it still does the samething. Still on 1.7.2

[cabaucom376]

You're running an old version of arcane that has references to the old repository before the migration to getarcane therefore it is failing. Try manually updating and then see how its does going forward.