rdmorganiser / rdmorganiser/rdmo-docker-compose
gunicorn failed to start during building
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm encountering an issue while attempting to run the RDMO Docker. After copying docker/baseconf.toml as conf.toml, I try to build the container using the make command. However, I end up in an infinite loop with the following message:
rdc-rdmo | Run gunicorn
rdc-rdmo | gunicorn failed to start, retry in 60s
I'm having trouble pinpointing the source of the problem. Any insights or suggestions would be greatly appreciated.
Thank you in advance!
Gautier
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker/baseconf.toml and the Makefile target invoked by make; then inspect the container output around the repeated gunicorn startup failure. Reproduce the build and identify why gunicorn exits, with completion marked by the container starting without the 60-second retry loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100