I am testing new self-hosted Baserow I just installed via stack on Portainer. The update to the latest version 1.27.2 was literally just a click of a button (update stack, re-pull new image, done). Really works for “code challenged” folk like me.
But the question I have if I can do something similar on my current production Baserow (containing important data) that was installed on different machine: Docker container (not stack) and could be managed via Portainer. Could I use Portainer to update it to the latest version? In Portainer, containers have “Recreate” button and when clicked “Re-pull image” option and warning that “any non-persisted data will be lost”. Just wanted some input if this is safe way to update baserow to the latest version and data not be lost. Thank you.
Hi!
While Portainer is not officially supported as a deployment method, it uses docker internally so the upgrade procedure should be similar to one we have described in our documentation: Install with Docker
So, yes, you should be able to upgrade Baserow by pulling a newer version of the image. Mind that you should perform a backup of your data (files and database).
You could install portainer’s docker image to the host where your baserow instance is running. As soon as portainer is setup it will have access to the docker daemon and you should be able to see all containers and stacks running on that system and interact with them.
After installing portainer you can manage all the containers on that host with it.
As @cezary already mentioned, please make sure make a backup 
Thank you vary much for the feedback. Sorry if I wasn’t clear: Portainer is already installed and running and I see baserow container there among others. My question was if it is safe to update baserow using Portainers “Recreate” button for that container. Anybody tried it? Thanks again.
Yes it is safe. I have done it multiple times on one of my instances without problem. Just did it for the 1.27 upgrade without problems