hussein-awala commented on issue #56545:
URL: https://github.com/apache/airflow/issues/56545#issuecomment-3393170021

   The change you mention was released in `5.2.1` more than 2 years and half 
ago, I'm surprised no one faced/reported the issue before. This would make 
sense if we have the folder `/airflow` created in the Docker image and we 
removed it recently, but according the blame history, it is not the case:
   ```log
    git blame Dockerfile | grep "/airflow"
   07fd0d71c8f (Jarek Potiuk       2020-04-02 19:52:11 +0200   43) ARG 
AIRFLOW_HOME=/opt/airflow
   3feb057f0ee (Jarek Potiuk       2022-01-08 20:41:29 +0100   46) ARG 
AIRFLOW_USER_HOME_DIR=/home/airflow
   94b03f6f432 (Jarek Potiuk       2021-08-04 23:32:12 +0200   62) ARG 
AIRFLOW_IMAGE_REPOSITORY="https://github.com/apache/airflow";
   7f02b4718bc (Kamil Breguła      2022-01-23 14:15:45 +0100   63) ARG 
AIRFLOW_IMAGE_README_URL="https://raw.githubusercontent.com/apache/airflow/main/docs/docker-stack/README.md";
   a1717a652b3 (Jarek Potiuk       2024-03-06 01:27:15 +0100   70) # 
SOURCES_FROM/TO with "." and "/opt/airflow" respectively - so that sources of 
Airflow (and all providers)
   14b00ed5e2c (Josef Šimánek      2025-06-22 11:57:12 +0200  892)     echo 
"${COLOR_YELLOW}See: 
https://airflow.apache.org/docs/docker-stack/build.html#adding-new-pypi-packages-individually${COLOR_RESET}";
   d4473555c0e (Jarek Potiuk       2025-04-02 13:11:13 +0200 1116)              
 --editable ./airflow-core --editable ./task-sdk --editable ./airflow-ctl \
   09544966741 (GPK                2025-09-11 20:37:02 +0100 1119)              
 --editable ./airflow-e2e-tests \
   9cbab95fd29 (Jarek Potiuk       2022-03-27 19:19:02 +0200 1474)     # HOME 
directory to the /home/airflow so that (for example) the ${HOME}/.local folder 
where airflow is
   14b00ed5e2c (Josef Šimánek      2025-06-22 11:57:12 +0200 1544)         >&2 
echo "     https://airflow.apache.org/docs/docker-stack/entrypoint.html";
   14b00ed5e2c (Josef Šimánek      2025-06-22 11:57:12 +0200 1558)         >&2 
echo "     https://airflow.apache.org/docs/docker-stack/entrypoint.html";
   9cbab95fd29 (Jarek Potiuk       2022-03-27 19:19:02 +0200 1601)     >&2 echo 
"         https://airflow.apache.org/docs/docker-stack/build.html";
   9cbab95fd29 (Jarek Potiuk       2022-03-27 19:19:02 +0200 1638) readonly 
DIRECTORY="${AIRFLOW_HOME:-/usr/local/airflow}"
   9cbab95fd29 (Jarek Potiuk       2022-03-27 19:19:02 +0200 1663) # The 
content below is automatically copied from 
scripts/docker/airflow-scheduler-autorestart.sh
   25b62a72f44 (Jarek Potiuk       2022-03-31 13:39:46 +0200 1664) COPY <<"EOF" 
/airflow-scheduler-autorestart.sh
   9cbab95fd29 (Jarek Potiuk       2022-03-27 19:19:02 +0200 1672)         date 
>> /tmp/airflow_scheduler_errors.txt
   7c12a9d4e0b (Jarek Potiuk       2020-06-16 12:36:46 +0200 1756) ARG 
AIRFLOW_REPO=apache/airflow
   d524cec99db (Jarek Potiuk       2021-02-21 18:56:55 +0100 1761) ARG 
CONSTRAINTS_GITHUB_REPOSITORY="apache/airflow"
   acff1296886 (Jarek Potiuk       2022-07-20 19:30:03 +0200 1778) # set to "." 
and "/opt/airflow" respectively.
   8e3d1fcff6c (Jarek Potiuk       2022-03-29 15:03:50 +0200 2015) COPY 
--from=scripts airflow-scheduler-autorestart.sh /airflow-scheduler-autorestart
   cf510a30fb4 (Jarek Potiuk       2020-06-27 14:29:55 +0200 2018) # See 
https://github.com/apache/airflow/issues/9248
   4620770af45 (Jarek Potiuk       2022-01-11 10:38:34 +0100 2037) # See 
https://airflow.apache.org/docs/docker-stack/entrypoint.html#signal-propagation
   2c6c7fdb230 (Jarek Potiuk       2021-01-21 16:16:09 +0100 2082)   
org.opencontainers.image.url="https://airflow.apache.org"; \
   94b03f6f432 (Jarek Potiuk       2021-08-04 23:32:12 +0200 2083)   
org.opencontainers.image.documentation="https://airflow.apache.org/docs/docker-stack/index.html";
 \
   ```
   
   Could you try reproduce the issue in the K8S integration tests? That way we 
can figure out where and how we should fix it.


-- 
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