Repository navigation
Conversation
| start_period: 30s | ||
| restart: always | ||
| networks: | ||
| - alertflow |
There was a problem hiding this comment.
Theres no need to expose the redis container to the external alertflow network, the default is enough
There was a problem hiding this comment.
Thank you, @luabida.
I added this because during the staging test the scheduler was attached to alertflow_alertflow, while Redis was attached to alertflow_default, so the scheduler could not resolve redis:6379.
The alertflow network here is a local bridge; only infodengue is external. If we want to keep Redis on the default network, I think we should instead make the core Airflow services use the default network consistently. I can adjust the compose that way.
| && /opt/airflow/envs/geospatial_env/bin/pip install --no-cache-dir --upgrade pip setuptools wheel \ | ||
| && /opt/airflow/envs/geospatial_env/bin/pip install --no-cache-dir -r ${AIRFLOW_HOME}/requirements-vegetation-metrics.txt | ||
|
|
||
| ENTRYPOINT [ "/entrypoint.sh" ] |
There was a problem hiding this comment.
Please keep the Dockerfile as it is, the Dockerfile and compose follow the Airflow docs config
2 participants
No description provided.