I am definitely it attempting to shift blame. The unfortunate thing with self hosted more specifically. Is not necessarily understanding the server OS. Most ppl install an OS and generally keep it upto date. But often with LTS may not know or understand upgrading the OS. Especially if they are used to rolling releases.
For example a company I help out after not updating for awhile noticed there was an update available. So they updated Docker through the web UI. Which then allowed them to update Discourse.
Due to the Ubuntu LTS not being new enough the docker update did not meet the minimum requirement. Which the web UI still allowed the update attempt. Which of course failed and took the site down.
So they attempted a command line rebuild which of course failed due to min requirements not met.
If the Updating in the web identified the Docker version was not minimum. It could have aborted the update process notifying an unmet dependency without the site going down.
I took a general look for them. As it appears they maybe running other things on the server. I have instructed them to have their tech look into upgrading the LTS to a newer version. As I did not want to try upgrading the OS in case it breaks other things they are running.
Is there an easy way to restart the container prior to the web.& Command line rebuild attempt?
I tried ./launcher start app
Which failed.
The other thing. Due to how discourse site went down can spinning up a new server with rsync work? They are running stable instead of the recommended tests passed.
If they run the :‘do-release-upgrade’ and manually upgrade Docker would this be effective to get the postgreq upgraded?