jtommi commented on PR #36611:
URL: https://github.com/apache/airflow/pull/36611#issuecomment-1878724030
Thanks for all those insights, very helpful.
I'm really sorry to have wasted both of your time @potiuk and @Taragolis
I was pretty confident because doing `docker-compose up airflow-init`
literally said
```
airflow_init_1 | ERROR: You need to initialize the database. Please run
`airflow db init`. Make sure the command is run using Airflow version 2.5.3.
airflow_init_1 | 2.5.3
```
... and looking into the command and /entrypoint, nowhere it ran `db init`
(which in hindsight makes sense if `airflow version` does initialize the DB.
I was testing around with 2.5.3 and 2.8.0 thinking I was modifying the
relevant things in the docker-compose file, spoiler, I wasn't.
In the end I wasn't able to reproduce the issue in 2.8.0 and for 2.5.3 it
failed because I was using _AIRFLOW_DB_MIGRATE: 'true' instead of
_AIRFLOW_DB_UPGRADE: 'true'.
That said, the output is still different, but not sure it's worth modifying
it, I got:
```
airflow_init_1 | [2024-01-05T12:52:27.886+0000] {override.py:1458} INFO -
Added user airflow
airflow_init_1 | User "airflow" created with role "Admin"
airflow_init_1 | 2.8.0
airflow_init_1 exited with code 0
```
And also, if all Airflow containers in the docker-compose are dependent on
airflow-init, why does the doc specify that you should run it first, since it
will run first anyway when you'll do `docker compose up`
--
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]
