potiuk commented on issue #27475: URL: https://github.com/apache/airflow/issues/27475#issuecomment-1303043604
Just use official Airflow image https://airflow.apache.org/docs/docker-stack/index.html . Also read the docs. If you start from what you used in Puckel - scratch it completely and follow the examples found here https://airflow.apache.org/docs/docker-stack/build.html. DON'T try to copy what you've done with Puckel. You will have many problems like this. Try to understand what it does and rather than blindly copying instructions from your Puckel image without understanding it, understand what yiou want to achieve and achieve the same by following the examples and learning how the new image works. The way permissions were defined in Puckel were abominations. They were primitive, unsecure and not following modern recommendations and best practices of docker images. Scratch that. It's basically "garbage-in" -> "garbage out" approache and other things will not work if you attempt to do so. In your above case - airflow has no "sudo" capabilities by design. Read about the permissions in the documentation above - everything that airflow wants to use has to be "airflow" group writeable (this is to make the image open-shift compatible). Follow examples to switch the user using `USER` command in the Dockerfile. Make sure that all folders you mount to dockerfile are owned by "airflow" group if you want to make them writeable. Just follow the docs.. And DON't try to copy lines from Puckel. -- 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]
