potiuk commented on issue #58509: URL: https://github.com/apache/airflow/issues/58509#issuecomment-3599568800
Actually .. Maybe this is the same reason as described in https://github.com/apache/airflow/issues/42195#issuecomment-3586845274 seems to be likely culprit. I have not yet looked at it but it seems that attempts of `.pyc` complation (unsuccesfull) due to lack of permission to write those files (that have ever changing random - or rather timestamp-derived names) might be the reason. Similarly to the old "official" Python images we are removing .pyc files during compilation, which significantly I have not thought yet what could be the best solution (maybe we shoudl **not** delete the .pyc files, or generate them in a different folder, or maybe disable writing the .pyc files - all have drawbacks and trade-offs) but one - easy way to check it is to make (just for tests) `/usr/local/lib/` group-writeable recursively (they should be owned by group 0, and all users that you can run airflow with should have group 0). Or you can simply run the containers with root user (that should nicely work as well in our officiall image - though obviously is not recommended normally). If anyone here could check if one of those changes fixes the issue, we could then discuss and decide how to adapt the image in the best way to fix the issue. -- 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]
