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. The causes of this issue are still not clearly identified, or confirmed. > 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. I thought I did set `AIRFLOW_UID` to 1001 and `AIRFLOW_GID` to 0 (manually) in the `.env` file. Is it not the same as doing `echo -e "AIRFLOW_UID=$(id -u)\nAIRFLOW_GID=0" > .env` ? > 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). I hope I am not badly mistaken about this, but if so, could you kindly clarify the misconception ?   > The solution you copied is to manually build image and there **manually** your UID as the user. Could you clarify what you mean by **manually**? Is it because I put it in the `.env` myself? As I have asked earlier, wouldn't the above mentionned command do just that? P.S : Please find the `.env` file content under the `docker-compose.yml` which was enclosed in the initial post, but 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]
