inflightfailure opened a new issue, #77220:
URL: https://github.com/apache/airflow/issues/77220

   ### What happened
   
   The official `apache/airflow:slim-3.4.0-python3.13` image is pinned to this 
hardened Python base image:
   
   ```text
   
ghcr.io/apache/airflow/base/python:3.13.18-debian13-dev@sha256:51014e49beb6ef57cd822eebedc2f242407ccadd54c8b39914aa4f067cc948e6
   ```
   
   That base image contains:
   
   ```text
   zlib1g     1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4
   zlib1g-dev 1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4
   ```
   
   The current DHI `3.13.18-debian13-dev` publication has moved to a newer 
immutable digest and contains the patched `deb13u1+dhi0` packages. However, the 
Airflow 3.4.0 image remains pinned to the older base digest, so downstream SBOM 
policy scans continue to report the old zlib components. Updating zlib in a 
derived image changes the final filesystem but does not remove the stale 
component inventory inherited from the Airflow base image.
   
   ### Airflow image
   
   ```text
   
apache/airflow:slim-3.4.0-python3.13@sha256:a08c6cf04a9312c3d39f7c7732c48906d7850add9d4b8630ce9c13ca29e95a17
   ```
   
   ### Expected behavior
   
   Please refresh and republish the Airflow 3.4.0 hardened image (or the next 
3.4 maintenance release) against a patched, immutable DHI base digest and 
publish the corresponding updated image SBOM/manifests.
   
   ### Related work
   
   This appears related to the hardened-image and pinned OS-dependency work in 
#76023, #76200, #76225, #76484, and #76485.
   
   ### Additional context
   
   The downstream use case is an Airflow 3.4.0 deployment using the slim image 
and the SFTP/SSH providers. The application image itself is otherwise 
functional; the release is blocked by the stale zlib inventory in the official 
base image.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to