I've currently deployed an airbyte instance on gcp...
# ask-community-for-troubleshooting
q
I've currently deployed an airbyte instance on gcp after using it locally for a while, and am setting up my connectors again, host.docker.internal isn't working anymore when im setting up a postgres instance, is there any way to restore all the pipelines/sources/destinations I had in my local deployment?
a
host.docker.internal is a Mac specific thing. You can use
localhost
instead, provided Cloud SQL Proxy is running on the same VM
c
You can export the configuration of your local instance to import them in your gcp instance... But some tweaks such as replacing by localhost might be necessary because of OS differences though...
q
sorry but could you guide me more or refer me to a doc if available regarding exporting my config to my instance
I've imported my local config but localhost doesn't seem to be working
c
You can follow the same workflow as for upgrading but in your case, you are using different host instances for the export/import: https://docs.airbyte.io/operator-guides/upgrading-airbyte
I’ve imported my local config but localhost doesn’t seem to be working
So what does your setup look like? you are deploying airbyte on a gcp instance but where is the postgres database deployed?
q
the postgres db is deployed locally
c
locally on the same gcp instance where airbyte is? are you able to connect to it using a different sql client? (which os is that using?)
q
would i need to run the cloud sql proxy on my gcp instance to make it possible?
yes this is the same instance i referred to you about here
c
would i need to run the cloud sql proxy on my gcp instance to make it possible? (edited)
yes, it seems you should do something along those lines… https://cloud.google.com/sql/docs/postgres/connect-admin-ip