potiuk edited a comment on issue #19962: URL: https://github.com/apache/airflow/issues/19962#issuecomment-1021417097
> Summarizing: following the steps in the documentation leads to an error in the container startup. @chriske - could you please open a new [discussion](https://github.com/apache/airflow/discussions) and explain all the details of errors, problems and how you tried to remedy it. Ideally a `gist` with logs and details of error message you had, and goal that you tried to achieve. There are many things you should check and describe: * What is your configuration you applied? * How did you check that the configuration is typo-free? * How did you check that airflow properly picked it up? * How did you expect it to be in your docker compose? * How does it look when you exec in your docker container? * What errors do you get? * What did you expect and what did you get instead ? Ideally showing the exact code and lists what you see in the container, including what you expected vs. what you see. What did you try to do to fix it? There are many ways how custom logging might/might not work and many ways how you can **think** your docker compose setup is right, where it is not - you really need to understand very well all the nuances of how docker compose works and how docker containers works inside - this is a knowledge outside of airflow, it's pretty generic `docker-compose` and `container` knowledge and experience, and in many cases users don't really understand some of the consequences. This might not be your case of course but from the very "terse" description no-one is able to tell if this is your configuration, or airlfow instructions, or unexpected docker-compose behaviour and consequence, or misuderstanding or bad assumptions on either side. Posting "same error" and "following the guide" is not nearly good enough to get any help with your problem. But if you describe your problem in detail in discussion, there is a chance that someone will help. -- 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]
