ImadYIdrissi edited a comment on issue #17320: URL: https://github.com/apache/airflow/issues/17320#issuecomment-889526816
I don't understand why this thread was closed. > Docker-Compose of Airlow is not production ready. You should use it only for development and testing I am not trying to use it for production, we are merely testing this approach, and trying to understand it. > you should make sure that you use your HOST_ID as user_id and GID=0 as user. OK so setting my UID manually in the `.env` file is not the same as doing `echo -e "AIRFLOW_UID=$(id -u)\nAIRFLOW_GID=0" > .env` ?? Wouldn't that just relace my `.env` file and remove my `AIRFLOW_HOME`?? plus my UID (1001) is already set within it? BTW the GID is already set to 0 **as a group** within it aswell... > BTW. I think you are not aware that your user changes when you run sudo... Most likely your logs/dags/ etc. file have been created as owned by that root user and this is causing all your permission problem. My dags, logs etc... are not root owned, they're user owned (UID : 1001).   > The solution you copied is to manually build image and there **manually** your UID as the user. I don't understand what you mean by **manually**, is it because I put it in the `.env` myself? Wouldn't your command do just that? P.S : Please find the `.env` file content under the `docker-compose.yml` which was enclosed in the initial post, it might have been easily missed as the main content is bigger. -- 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]
