You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
afabiani opened this issue
Aug 26, 2022
· 0 comments
Assignees
Labels
3.3.x4.0.xdockerIssues specific to GeoNode docker or GeoNode SPCmajorA high priority issue which might affect a lot of people or large parts of the codebasemaster
In the docker-compose.yml a health for the django container is performed using a simple curl command inside in the container to check if the server is running: test: "curl --fail --silent --write-out 'HTTP CODE : %{http_code}\n' --output /dev/null http://127.0.0.1:8000/"
But this isn't working anymore since in the default configuration an http-socket isn't configured, this results in curl exiting with code 52 as its getting an empty reply from the server.
This results in a permanent unhealthy status of the container and is misleading.
A solution would be to use uswgi_curl from the uwsi-tools package (pip). It does not offer the same options as curl but results in a correct exit code (0 working, 1 not working).
The text was updated successfully, but these errors were encountered:
3.3.x4.0.xdockerIssues specific to GeoNode docker or GeoNode SPCmajorA high priority issue which might affect a lot of people or large parts of the codebasemaster
References: GeoNode/geonode-project#363
In the
docker-compose.yml
a health for the django container is performed using a simple curl command inside in the container to check if the server is running:test: "curl --fail --silent --write-out 'HTTP CODE : %{http_code}\n' --output /dev/null http://127.0.0.1:8000/"
But this isn't working anymore since in the default configuration an http-socket isn't configured, this results in curl exiting with code 52 as its getting an empty reply from the server.
This results in a permanent unhealthy status of the container and is misleading.
A solution would be to use uswgi_curl from the uwsi-tools package (pip). It does not offer the same options as curl but results in a correct exit code (0 working, 1 not working).
The text was updated successfully, but these errors were encountered: