Kamaldeen Samaila
05/25/2024, 6:45 PMkapa.ai
05/25/2024, 6:45 PMbash docker-compose down -v 2. Remove the data on disk: bash rm -rf /tmp/dev_root rm -rf /tmp/airbyte_local 3. Remove Docker volumes associated with Airbyte: bash docker volume rm $(docker volume ls -q | grep airbyte) 4. Optionally, prune all Docker volumes and system: This step is useful if you've been modifying image tags while developing. bash docker system prune -a docker volume prune 5. Rebuild the project (if you are developing locally): bash SUB_BUILD=PLATFORM ./gradlew clean build VERSION=dev docker compose up -V ### Additional Considerations - If you are working on Python connectors, you may also need to reset the virtualenv and re-install the connector's dependencies: bash # Assuming you have a virtualenv loaded into your shell deactivate # From the connector's directory # remove the venv directory entirely rm -rf .venv # make and activate a new venv python3 -m venv .venv source .venv/bin/activate pip install -e ".[dev]" ### References - [Resetting the Airbyte Developer Environment](https://docs.airbyte.com/contributing-to-airbyte/resources/developing-locally#resetting-the-airbyte-developer-environment) - [Upgrading on Docker](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-docker) - [Creating a Python Destination (DuckDB) - Resetting Airbyte](https://airbyte.com/tutorials/creating-duckdb-destination-with-python) By following these steps, you should be able to clean up your server and prepare it for a fresh install of Airbyte on Docker.