Migrate docker images to latest debian

[AntonioKL]

What

This PR migrates Docker images from deprecated Debian Buster and other outdated base images to their latest stable and supported versions. This ensures improved security, stability, and maintainability across Airbyte's Dockerized components.

How

The migration involved updating approximately 254 Dockerfiles across the repository. Key changes include:

• Ubuntu Migrations: Upgraded ubuntu:18.04 to ubuntu:24.04 (latest LTS).
• Python Debian Migrations (slim): Updated python:3.9-slim, python:3.10-slim, python:3.9-slim-bullseye, and python:3.10-slim-bullseye to use *-slim-bookworm (Debian 12).
• Python Debian (full): Upgraded python:3.9.11 to python:3.9-bookworm.
• Python Alpine Migrations: Updated various python:X.Y-alpine3.15 and python:X.Y-alpine3.18 images to python:X.Y-alpine3.20 (latest Alpine). Also upgraded python:3.7.11-alpine3.14 to python:3.9-alpine3.20 due to Python 3.7 End-of-Life.
• Node.js Migrations: Upgraded node:16-alpine to node:20-alpine3.20 (LTS version).
• Amazon Linux Migrations: Updated amazonlinux:2022.0.20220831.1 to amazonlinux:2023.
• DBT Image Migration: Changed fishtownanalytics/dbt:1.0.0 to the new official image location ghcr.io/dbt-labs/dbt-core:1.7.4.
• Package Fixes: Ensured apt-get update is run before apt-get upgrade in octavia-cli/Dockerfile.

Recommended reading order

N/A (changes are spread across many Dockerfiles, primarily base image tags)

🚨 User Impact 🚨

This is an internal infrastructure update focused on security and maintainability. There are no breaking changes for end-users. Connectors affected by these base image updates will receive a patch version bump.

Pre-merge Actions

Updating a connector

Community member or Airbyter

• Grant edit access to maintainers (instructions)
• Unit & integration tests added

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• If new credentials are required for use in CI, add them to GSM. Instructions.

---

 

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

Important: This command can only be run by one of the repository admins:
Usage: ./tools/bin/get_repo_admins.sh <personal_access_token>

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.