Persistence on Google Cloud Compute Engine after restart

I have Airbyte running on GCP Compute engine as specified in the documentation here.

We are running into issues SSHing into the container and I want to restart it as a troubleshooting step, but I want to ensure that our config/state will not be lost.

Looking at the docker-compose it seems like the postgres database data is persisted on the disk and we have a persistent disk in GCP, so this should be fine, but I wanted to confirm.

Hey @wjwatkinson,
You can restart Airbyte without worrying about data loss.
The DB data is persisted in the airbyte_db docker volume. The volume is not removed by a docker-compose down or upcommand.

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.