Something seems to have changed dramatically in th...
# troubleshooting
c
Something seems to have changed dramatically in the way Airflow behaves upon container init between Meltano 1.83 and 2.1.0. Airflow is running immediately on meltano install, well before any env vars are set in my entrypoint. It didn't used to do this. Under 1.83 with Airflow 2.1.2, it was happy to be installed and remained stopped until I started it after the environment was setup in the entrypoint.