Keywords: Apache Airflow - Microsoft Azure - Technical issue - Other
We are deploying airflow into Azure AKS using the Bitnami Airflow Helm Chart which calls the following Dockerfile: https://github.com/bitnami/bitnami-docker-airflow-worker/blob/master/1/debian-10/Dockerfile
We noticed that when the container comes up, it always runs
airflow initdb and airflow resetdb, even though the DB is available and initialized. We want to understand why does bitnami initialize the db, everytime the container comes up?
Also, we notice that this causes a lot of startup time and the container takes > 15 minutes - 45 minutes (depending on the size of the dag files/how old the Db is?). Can you please help us understand what could be causing the delay?