Cannot connect to the webserver with docker #22230
Replies: 2 comments 4 replies
-
|
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
|
You likely have a hardware problem with your MacBook. Try a different machine. |
Beta Was this translation helpful? Give feedback.
-
|
I have a similar problem where the scheduler can not connect to the webserver. I am running v2.3.3 in Docker containers. I have the webserver coming up correctly and can connect to the webserver just fine. The webserver runs behind a Traefik proxy. When I bring up the scheduler I get the following output: Two notes about the above.
I installed The above packets continually get transmitted until the container exits out. Now the only reference to airflow.wt0f.com in is in the The real problem I have been having is that scheduler is trying to connect to the webserver on port 8080. This port is not exposed because of the Traefik proxy. The webserver is only exposed on port 443. I am not able to find a configuration setting that will allow me to instruct the scheduler to connect on a specified port. Given the update I have above, I have tried setting I seem to be having the same problem with the worker. So running a single worker can be made to work if the worker is on the same host and connected to the same Docker network. But if I run a worker on another host I am going to run in to the same problem again if the port can not be specified. Is there a way to specify what port the webserver is running on? Also given that I run it on port 443, how do I tell scheduler and worker to use TLS? |
Beta Was this translation helpful? Give feedback.
-
|
Those are great questions that should be asked in Bitnami repository. The community here has no access/control/knowledge about the bitnami charts. We have no influence, knowlege what they do and how. It's even written in the output you got: We will be more than happy to answer similar questions if you use the Airflow Community official image https://airflow.apache.org/docs/docker-stack/index.html and Airflow Official Helm Chart - https://airflow.apache.org/docs/helm-chart/stable/index.html but when you have problem which looks like deployment related and you use bitnami containers and chart - you should check with them :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi @hickey, I was in the same situation as you, in my case, I deployed airflow to k8s and in Then I did a weird implementation, it worked fine again and was able to connect to |
Beta Was this translation helpful? Give feedback.
-
|
@quocanh-upmesh what did you do to fix it? i am facing same issue |
Beta Was this translation helpful? Give feedback.
-
Describe the issue with documentation
I have followed this doc to try and run airflow with docker : https://airflow.apache.org/docs/apache-airflow/stable/start/docker.html
When I run the docker-compose with "docker-compose up", containers are unhealthy and I cannot connect to the webserver.
I know the memory is critical, so I went to Resources and increased it to the maximum I could on my machine.
Here are the logs from the terminal:
Not really sure what the problem is. When trying to connect to the webserver it does not work.
How to solve the problem
Is it related to my machine ? It's a macbook air from 2015... I though it would be enough.
Is there another way to run airflow and try to run dags ?
Anything else
Every Time.
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions