potiuk commented on PR #34804: URL: https://github.com/apache/airflow/pull/34804#issuecomment-1812081368
> That said, I'm considering running airflow in production on arm64 servers, how far is it from being production ready? I've searched for a page with the roadmap or status of the arm build, but couldn't find one. It used for development mostly and it waits until we run a complete suite of tests on ARM to be able to remove the "experimental" tag - which is going to happen when we switch our CI infrastructure to K8S-run when we will be able to chess the runner freely. > The problem is that airflow locks down the image and by doing so doesn't make it possible to install such dependency without having to resort to write your own Dockerfile. It's simply not true. Airflow does not "lock-down" anything. It sets user to non-root (as all production images should do). And you can still change the user to root for isntallation . This is not only possible, but explained in our documentation and examples as I pointed out. Just read it. If you read the docs, you can also find out that this is highly optimized image that deliberatly does not have build-essentials. Also if you read them further you will find that Airflow image is "reference" one and if you have any needs that go beyond it - you can also use airflow Dockerfile to build your own, customized version of it that fits your need. Ultimately there are no "guarantees" this image gives anyway and you are responsible to make sure you have what you need for your production need. BTW. Airflow (and it's image) comes for fee and with no guarantees whatsoever so the experimental status is nothing more than indication we are not fully testing it in CI and tha things might change abruptly there as we might find a need to add/remove thigns in next version in order to fix some problems we are not aware of. So this is not an issuse of Airflow at all anyway - regardless. Still I am happy to point you to the docs so that you can do whatever you need for your case. -- 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]
