airflow-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Standish <>
Subject Re: Airflow-Init stuck at initialization
Date Mon, 16 Aug 2021 17:29:14 GMT
Let me offer a suggestion.

I think it's helpful to simplify things and isolate components.  To that
end what you could do is scrap docker for a moment.  Create a
python virtualenv in your host.  Install airflow into this virtualenv. Set
AIRFLOW__CORE__SQL_ALCHEMY_CONN as appropriate and run airflow in the
virtualenv.  Then you'll be able to confirm the issue is docker and not
some other connectivity issue.

Next move on to docker, perhaps without compose.  One thing you could do is
get a terminal in a running container and try to connect to this server
e.g. using telnet or psql (you might have to install these).  Then you'll
figure out what connection string will actually work and it's just a matter
of setting up the env vars correctly for airflow to connect in the right

Also, are you using the official apache-airflow image?  If not, I would
recommend that.

On Mon, Aug 16, 2021 at 10:22 AM Anthony Joyce <> wrote:

> Hi Daniel,
> Thanks for the suggestion! I’m new at Docker so apologies if some of the
> configs are incorrect. Still learning.
> I removed service Postgres since I am using my local db. Still stuck on
> *airflow-init*. There are no log entries that explain what it is doing or
> what it is waiting for, but obviously *airflow-init *is waiting for
> something. I’ve since restarted docker service, flushed iptables chains
> relating to Docker, restarted again. Still stuck.
> Anthony
> On Aug 16, 2021, at 1:11 PM, Daniel Standish <> wrote:
> If you are using an already existing postgres, then why are you running
> postgres service in compose?
> If that's *not* the database you are connecting to, then you should
> remove it from your compose file. (conversely if you *are* trying to use
> compose postgres, then we might have some configuration suggestions to
> offer)
> ---
> Separately, on mac compose, for the container to access host i think you
> might need to add svc.localhost or something like that... there are SO
> posts on this topic eg

View raw message