sjyangkevin commented on issue #54402:
URL: https://github.com/apache/airflow/issues/54402#issuecomment-3322133067

   I attempted to follow the same setup but wasn't able to reproduce the issue. 
I guess probably because the way to set the environment variable is different. 
Below is my step.
   
   I am following this guide to run Airflow inside Docker: 
https://airflow.apache.org/docs/apache-airflow/stable/howto/docker-compose/index.html#running-airflow-in-docker
   
   Then, I set the `AIRFLOW__API__BASE_URL` in the `docker-compose.yml` file.
   ```
     environment:
       &airflow-common-env
       AIRFLOW__CORE__EXECUTOR: LocalExecutor
       ...
       AIRFLOW__API__BASE_URL: 'http://myDomain.com/airflow'
   ```
   After that, `docker compose run airflow-cli airflow config list` shows that 
the `base_url` is set in the config. I also attempted to seek for the 
`base_url` in the running container and found out this is set properly.
   
   I am wondering if the `AIRFLOW__API__BASE_URL` is set by directly export the 
environment variable in the running container. If so, we might need to restart 
all the airflow components to pick this up. Please correct me if I am wrong.
   
   Below is my test results.
   
   ### Airflow 3.0.6
   <img width="1147" height="621" alt="Image" 
src="https://github.com/user-attachments/assets/dc7672a2-0bb9-44be-a17d-df9c635ebfcf";
 />
   <img width="1624" height="747" alt="Image" 
src="https://github.com/user-attachments/assets/2065cb39-08f6-479d-854e-86279282621b";
 />
   
   ### Airflow 3.0.4
   <img width="1624" height="739" alt="Image" 
src="https://github.com/user-attachments/assets/47df22eb-190d-458a-bbf7-984956f12609";
 />
   <img width="1624" height="782" alt="Image" 
src="https://github.com/user-attachments/assets/6430ffaf-6791-4e0b-9d98-e34ef1ce50c5";
 />


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