I have been doing web based upgrades at admin/upgrade and since I tend to have very high up times, does this replace replace the updates that are done when rebuilding the container with ./launcher rebuild?
Also, when I reboot does the container auto-update itself?
Majority of your updates can be done via the web, once in a few months you need to rebuild to get updates to the base image. If we deem it critical we will force it upon you.
It seems to be working, but for some reason the log file get cut after Removing old container.
Is there some kind of recommended way to get automatic updates working?
I had to wait 300 seconds for the docker daemon to start. With this settings it should take 10 min after reboot to be back on air. Rebuilding takes 5 min with a SSD and 2 vCPU.
When there is a change to postgres or redis. Knowing when this has happened is a matter of keeping track of things and is the reason that many people think that the two container setup is too hard. I have scripts that check postgres and redis versions and upgrade the data container if a change has been made. Those changed happen every year or two, though sub-base upgrades happen a bit more often. Generally if you don’t upgrade from 13.1 to 13.5 it won’t matter much.