[GitHub] [airflow] potiuk commented on issue #26492: Cannot fetch log from Celery worker

[GitBox <gi...@apache.org>]

potiuk commented on issue #26492:
URL: https://github.com/apache/airflow/issues/26492#issuecomment-1329780031

   > Hi @potiuk , I ran into this error on 2.4.3. The env I'm using is directly from the official docker compose file from [here](https://airflow.apache.org/docs/apache-airflow/2.4.3/docker-compose.yaml).
   The way to reproduce it is to create and run a simple dag and check the log from UI.
   Thanks for looking into it.
   
   Just to clarify ut - the docker compose is NOT official compose. It's a quick-start docker compose that can get you up an running but if you have anu problems with it (in your environment) you should apply your docker compose expertise to be able to analyse it, I am afraid (and this is very clearly written [here](https://airflow.apache.org/docs/apache-airflow/2.4.3/howto/docker-compose/index.html) as "Caution".
   
   > This procedure can be useful for learning and exploration. However, adapting it for use in real-world situations can be complicated. Making changes to this procedure will require specialized expertise in Docker & Docker Compose, and the Airflow community may not be able to help you.
   
   > For that reason, we recommend using Kubernetes with the [Official Airflow Community Helm Chart](https://airflow.apache.org/docs/helm-chart/stable/index.html) when you are ready to run Airflow in production.
   
   I just followed (again as a million times before) all the steps one-by-one from our quick-start and unfortunately I cannot reproduce your problem. This is what I get. 
   
   <img width="2021" alt="Screenshot 2022-11-28 at 22 23 02" src="https://user-images.githubusercontent.com/595491/204383801-b210587c-a073-4a99-9032-7be2c8354f5d.png">
   
   So NO. It's not easily reproducible. You have to do better.
   
   Docker compose functionality depends on many local factors. This is one of the reasons why we do not recommend people who are not already experts in docker compose to use it - there is a learning curve involved and unfortunately when someone has expectations that things will "just work", they are gravely mistaken. You need to dive deep and understand a lot that happens under the hood in order to actually run anything (not only airflow) in docker compose. And we just warned you that you need to do a lot of investigations on your own - and provide useful information if you want help. Writing "it does not work for me" is not a useful information that will help those who want to help in their free time (because this is what is happening here - I am responding to you in my free time). But you give me little chance to help me without spending your own time first.
    
   If you want any help for your case where likely you have some misconfiguration of some sort. We are not ablet to magically guess with your docker, docker-compose configuration unfortunately - and if you really need some help with solving your problem 
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org