what type of document I have inside of the linux below path......I want to clean up machine is running out space: /var/local-path-provisioner/airbyte-local-pv/job-logging/workspace

Based on the knowledge sources, the path you're referring to contains Airbyte sync job logs. This is the workspace directory where Airbyte stores logs generated during sync jobs. Specifically, the files inside this directory are log files from Airbyte's job execution, including things like: •

logs.log

– the main sync log file •

catalog.json

– stream catalog information •

tap_config.json

/

target_config.json

– connector configuration files [Browsing Output Logs] How to Clean Up You can safely delete the files and folders inside this workspace/job-logging directory to free up disk space. This is a known and accepted approach. [MinIO Storage Full] Preventing Future Space Issues To avoid running out of space again, you can configure Airbyte to automatically clean up logs more frequently by setting the following environment variable:

env_vars:
  TEMPORAL_HISTORY_RETENTION_IN_DAYS: 7  # Default is 30 days

Reducing this value (e.g., to

7

days) will cause Airbyte to sweep old workspace/log files more frequently. [Log Sweeping; Quickly Run Out of Storage] > Note: The default retention is 30 days, which can cause the storage to fill up quickly if you have frequent or large syncs. Adjusting

TEMPORAL_HISTORY_RETENTION_IN_DAYS

is the recommended long-term solution. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai how to cleanup current logs

Based on the knowledge sources, here's how to clean up the logs in your path `/var/local-path-provisioner/airbyte-local-pv/job-logging/workspace`: Option 1: Delete Logs Directly in the Pod/Container If you're running on Kubernetes, exec into the MinIO pod and delete the log files:

kubectl exec -it <minio-pod-name> -n <namespace> -- bash

Then delete the contents of the log directories:

/storage/airbyte-storage/job-logging/workspace

You can also optionally clean up:

/storage/airbyte-storage/workload/output

[Sync Jobs Hanging] Option 2: Delete Files from the Host Path Directly Since your path is a local PV (

/var/local-path-provisioner/...

), you can delete the contents directly from the Linux host:

rm -rf /var/local-path-provisioner/airbyte-local-pv/job-logging/workspace/*

This will remove all log files while keeping the directory structure intact. [MinIO Cleanup] > ⚠️ Note: Deleting logs will clear all historical sync logs from the Airbyte UI. Your connections, credentials, and configurations will not be affected. Prevent Future Buildup After cleaning up, set a shorter log retention period to avoid this happening again:

env_vars:
  TEMPORAL_HISTORY_RETENTION_IN_DAYS: 7

You can also increase the MinIO PVC size in your

values.yaml

if needed:

minio:
  storage:
    volumeClaimValue: 2Gi

[Sync Jobs Hanging; Log Sweeping] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai which folder else I can clean?

Based on the knowledge sources, here are the additional folders you can clean up: 1. *Workload output directory:*/storage/airbyte-storage/workload/outputThis stores workload output data and can also consume significant space. [Sync Jobs Hanging] 2. On Docker deployments, the following volume is known to grow large:/var/lib/docker/volumes/airbyte_workspace/_dataThis is the main Docker named volume (

airbyte_workspace

) where Airbyte stores workspace data including logs and connector config files. [Quickly Run Out of Storage; Browsing Output Logs] > ⚠️ Reminder: Cleaning these folders will remove historical sync logs visible in the Airbyte UI, but will not affect your connections, credentials, or configurations. After cleaning up, make sure you have the retention policy set to prevent future buildup:

env_vars:
  TEMPORAL_HISTORY_RETENTION_IN_DAYS: 7

👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai I'm at var/lib there is no docker folder airbyte 2.0

That makes sense — in Airbyte 2.0 on Kubernetes, the storage architecture is different from Docker-based deployments. Instead of Docker volumes under

/var/lib/docker/

, logs are stored in MinIO (or a configured object storage), which is backed by a Kubernetes Persistent Volume. So the relevant paths to clean up would be inside the MinIO pod/storage, not under

/var/lib/docker/

. Based on the knowledge sources, the directories to target are: •

/storage/airbyte-storage/job-logging/workspace/

•

/storage/airbyte-storage/workload/output/

[Sync Jobs Hanging; MinIO Cleanup] The knowledge sources do not explicitly describe the exact filesystem layout for Airbyte 2.0's local path provisioner beyond what's been mentioned. However, since you found the logs at

/var/local-path-provisioner/airbyte-local-pv/job-logging/workspace

, that is your equivalent path on the host — you can clean that directory directly from the Linux host as discussed previously. > ⚠️ If you're unsure about other directories under

/var/local-path-provisioner/

, I'd recommend being cautious and only deleting contents of known log directories (

job-logging/workspace

and

workload/output

) to avoid accidentally removing configuration or database data. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai can I delete data from ./workload/output dir?

Yes, you can delete data from the

workload/output

directory. It is explicitly mentioned as a safe cleanup target alongside the job-logging workspace directory. [Sync Jobs Hanging] Based on your setup, the path would be:

rm -rf /var/local-path-provisioner/airbyte-local-pv/workload/output/*

> ⚠️ This will remove workload output data, but your connections, credentials, and configurations will not be affected. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.