When upgrading Airbyte, how do I update the environment variable? When

./run-ab-platform.sh -r

is run, the .env file gets wiped

When upgrading Airbyte, the environment variables are defined in your

.env

file. If you run

./run-ab-platform.sh -r

, it will remove the previous local

docker-compose.yaml

and

.env

files. If you want to update the environment variables, you should do it manually in the

.env

file before running the upgrade commands. Here are the steps to upgrade Airbyte on Docker: 1. Turn off Airbyte:

bash docker compose down

2. Upgrade the docker instance to the new version. If you are running Airbyte from a cloned version of the Airbyte GitHub repo and want to use the current most recent stable version, just run

git pull

. 3. If you are running Airbyte from downloaded

docker-compose.yaml

and

.env

files without a GitHub repo, run the following command to download the installation script:

bash wget <https://raw.githubusercontent.com/airbytehq/airbyte/master/run-ab-platform.sh>

4. Remove previous local

docker-compose.yaml

and

.env

files:

bash ./run-ab-platform.sh -r

5. Bring Airbyte back online, optionally with the

-b

flag to run the containers in the background (docker detached mode):

bash ./run-ab-platform.sh -b

Remember to update your

.env

file with the necessary environment variables before running the upgrade commands. For more details, you can refer to the [official documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte).

@hong-gyu Just incase this may be happening to you. I ran into a simple problem where I forgot that wget downloads the "run-ab-platform.sh" file as "run-ab-platform.sh.1". When I ran "run-ab-platform.sh", I was running the old version.