This message was deleted.
# ask-ai
s
This message was deleted.
k
You’re running an older, Docker Compose–based Airbyte (0.63.2) on RHEL and have vulnerability findings in OpenSSL inside the Airbyte containers. With the information available, there are two key points: 1. You cannot patch OpenSSL inside existing Airbyte images in-place in a supported way. The OpenSSL libraries are part of the container base images; fixing these requires updating to images that include patched dependencies, not changing the libraries inside running containers. The release notes confirm that newer Airbyte platform versions regularly update base images specifically to address security vulnerabilities.[[Airbyte 1.5 patches](https://docs.airbyte.com/release_notes/v-1.5#patches); [Airbyte 1.6 patches](https://docs.airbyte.com/release_notes/v-1.6#patches)] 2. Docker Compose is deprecated; upgrades should move you off Docker Compose. Airbyte has announced the deprecation of Docker Compose and provides a migration guide from Docker Compose to
abctl
.[[Airbyte 1.0 notes](https://docs.airbyte.com/release_notes/v-1.0#announcements)] The support QA snippet you shared also states that for Docker Compose you must migrate to
abctl
instead of continuing with
docker-compose
-based upgrades. Given your constraints (“step by step without affecting 7–8 containers and ~80 sync jobs”), the documentation and knowledge sources unfortunately: - Do not provide a supported, step‑by‑step procedure to patch OpenSSL within 0.63.2 Docker images in-place. - Do not describe an officially supported “no‑downtime” upgrade path for Docker deployments. In fact, an official forum answer explicitly states that upgrading Docker Airbyte without downtime isn’t currently possible; containers need to be stopped and restarted to pull the new version.[[Upgrade without downtime](https://discuss.airbyte.io/t/619)] What is documented and supported: 1. Security vulnerability handling process Airbyte explicitly asks that vulnerabilities not be handled via public GitHub or forums, but instead via the security email. [[Security reporting](https://docs.airbyte.com/platform/operating-airbyte/security#reporting-vulnerabilities)] Since you have specific OpenSSL findings in an older, on‑prem Docker deployment, the recommended channel is: - Email the Airbyte security team at the address in the security docs and: - Provide your current version (0.63.2), deployment method (Docker Compose on RHEL 8.10), and the exact OpenSSL findings. - Ask for the recommended target Airbyte version with patched base images compatible with your setup, and for any migration/upgrade guidance that minimizes downtime. 2. Upgrade / patch strategy (high level, from available docs) The documented pattern for addressing such vulnerabilities is: - Upgrade Airbyte to a version whose base images have been patched. Many later 1.x patch releases explicitly note “base images have been updated to address security vulnerabilities.”[[Airbyte 1.5 patches](https://docs.airbyte.com/release_notes/v-1.5#patches); [Airbyte 1.7 patches](https://docs.airbyte.com/release_notes/v-1.7#patches)] - For installations currently on Docker Compose, Airbyte recommends migrating to
abctl
using the migration guide
, rather than continuing to upgrade Docker Compose directly.[[Airbyte 1.0 notes](https://docs.airbyte.com/release_notes/v-1.0#announcements)] However, the knowledge sources you provided: - Do not include a concrete, step‑by‑step, Docker‑Compose‑to‑abctl migration procedure that guarantees no impact on existing connections/syncs, only the existence of a migration guide. - Do not describe a way to keep all existing jobs running while you upgrade images; on Docker the documented stance is that you must stop containers for an upgrade.[[Upgrade without downtime](https://discuss.airbyte.io/t/619)] Because of this, I cannot honestly give you the detailed, “no impact” step‑by‑step procedure you requested strictly from the documentation you shared. Recommended next action (based on docs): 1. Engage Airbyte security directly using the email in the security documentation, with your vulnerability report and environment details, and ask: - Which Airbyte version you should target to get patched OpenSSL/base images. - Whether there is a documented, low‑downtime migration/upgrade path from 0.63.2 Docker Compose to that version for an on‑prem VM deployment. 2. Plan a controlled maintenance window for either: - Migrating from Docker Compose to
abctl
using the official migration guide referenced in the 1.0 release notes, or - Upgrading to a newer, patched Docker‑based deployment if security or support confirms that as acceptable for your case. If you can share the exact migration/upgrade guide content (URL or text) you’re allowed to use, I can then help you interpret it and outline a concrete sequence tailored to your current 0.63.2 / Docker Compose setup.
A message from kapa.ai
Based on the docs and forum content you shared, there are two distinct, documented paths for moving off your old Docker images: 1. Migrate from Docker Compose to abctl (recommended, since Docker Compose is deprecated). 2. **General pattern for upgrading (requires stopping Airbyte; no zero‑downtime option).**[[Upgrade without downtime](https://discuss.airbyte.io/t/619); [Airbyte 1.0 notes](https://docs.airbyte.com/release_notes/v-1.0#announcements)] The sources do not provide a detailed, version‑specific, Docker‑Compose‑only upgrade procedure for 0.63.2, so I’ll stick to what is documented. --- ## Option 1 – Migrate from Docker Compose to
abctl
(recommended) The docs say Docker Compose is deprecated and you should migrate to
abctl
.[[Airbyte 1.0 notes](https://docs.airbyte.com/release_notes/v-1.0#announcements)] For migrating existing Docker Compose data, the documented steps are: 1. Stop your existing Docker Compose instance
Copy code
bash    docker compose stop
or, depending on your setup:
Copy code
bash    docker-compose stop
This ensures no writes while you migrate. [[Migrating from Docker Compose 1.6](https://docs.airbyte.com/platform/1.6/deploying-airbyte/migrating-from-docker-compose); [Migrating from Docker Compose next](https://docs.airbyte.com/platform/next/deploying-airbyte/migrating-from-docker-compose)] 2. Install / update
abctl
Copy code
bash    curl -LsfS https://get.airbyte.com | bash -
This gives you the latest
abctl
that knows how to deploy newer, patched images. [[Migrating from Docker Compose 1.6](https://docs.airbyte.com/platform/1.6/deploying-airbyte/migrating-from-docker-compose); [Migrating from Docker Compose next](https://docs.airbyte.com/platform/next/deploying-airbyte/migrating-from-docker-compose)] 3. **(If you’re not using an external DB or secret manager)** Run the migration install:
Copy code
bash    abctl local install --migrate
This command reads your existing Docker Compose data and migrates it into the new `abctl`‑managed deployment, using new images. [[Migrating from Docker Compose 1.6](https://docs.airbyte.com/platform/1.6/deploying-airbyte/migrating-from-docker-compose); [Migrating from Docker Compose next](https://docs.airbyte.com/platform/next/deploying-airbyte/migrating-from-docker-compose)] 4. **(If you are using an external DB or secret manager)** Docs say you do not need
--migrate
. Instead you must: - Create
values.yaml
and
secrets.yaml
for your deployment. - Then run:
Copy code
bash      abctl local install --values ./values.yaml --secret ./secrets.yaml
[[Migrating from Docker Compose 1.6](https://docs.airbyte.com/platform/1.6/deploying-airbyte/migrating-from-docker-compose); [Migrating from Docker Compose next](https://docs.airbyte.com/platform/next/deploying-airbyte/migrating-from-docker-compose)] 5. Verify the new deployment Use:
Copy code
bash    abctl local status
to confirm the version and that all components are healthy; then log into the UI and check that your connections and jobs exist as expected. [[Upgrading with abctl 1.6](https://docs.airbyte.com/platform/1.6/operator-guides/upgrading-airbyte); [Upgrading with abctl platform](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)] After this, future upgrades are straightforward:
Copy code
bash abctl local install
to move to the latest version with updated base images. [[Upgrading with abctl 1.6](https://docs.airbyte.com/platform/1.6/operator-guides/upgrading-airbyte); [Upgrading with abctl platform](https://docs.airbyte.com/platform/operator-guides/upgrading-airbyte)] --- ## Important limitations from the docs - No zero‑downtime upgrade for Docker: The official answer for Docker says you must stop containers to upgrade; there’s no documented “no downtime” method.[[Upgrade without downtime](https://discuss.airbyte.io/t/619)] - Docker Compose is deprecated: The docs recommend migrating to
abctl
rather than continuing with Docker Compose upgrades.[[Airbyte 1.0 notes](https://docs.airbyte.com/release_notes/v-1.0#announcements)] - The sources do not show a supported method to “just rebuild one or two containers with patched OpenSSL” for 0.63.2; the supported path is to move to newer images via migration/upgrade as above. Within these documented constraints, the most accurate step‑by‑step to “restart affected containers with new images” is: stop your Docker Compose deployment, migrate to
abctl
using
abctl local install --migrate
, and then run on the new images managed by
abctl
.