-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DJango container fails silently - Cannot deploy #12936
Comments
Update: I manage to start geonode with a hack. But I don't understand why I have to do this. First, I modify the stack file django container: django:
<< : *default-common-django
environment:
- IS_CELERY=False
entrypoint: ["/usr/src/geonode/entrypoint.sh"]
#command: "uwsgi --ini /usr/src/geonode/uwsgi.ini"
command: "python3 manage.py runserver 0.0.0.0:8010" # <--- Add this dummy process to avoid the container to restart
healthcheck:
test: ["CMD", "curl", "-f", "-s", "http://localhost:8010/"] # <-- just so is marked as healthy
interval: 30s
timeout: 30s
retries: 5
start_period: 30s
networks:
- geonode-network Start the stack, wait till is up and running, once is done open a shell and execute manually the command to start the web server So if this works, why I need to do this hacky thing? The problem with this "solution" is that I have to manually intervene. |
is there something present in the geonode log? |
The last time I checked was empty (It's tricky since it restarts by itself). Even though may not be useful, this is what I get when starts manually:
|
I'm not able to deploy the full stack of geonode. Django container keeps restarting in a loop, I guess because uwsgi fails silently, but there is nothing in the logs to point out what is the problem.
Here is my stack file (Docker Swarm):
And here are the last lines in django container logs (No migration errors, etc):
The rest of containers are up and running and nginx returns 502 since uwsgi does not start? If I change uwsgi with python dev server geonode starts and do not reset, but the frontend has issues and obviously using the python server is not a good idea, but shows that must be something wrong with uwsgi.
The text was updated successfully, but these errors were encountered: