sameersbn / sameersbn/docker-gitlab
could not fork new process for connection: Resource temporarily unavailable
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi!
I started to install Gitlab with Docker Compose, with the simplest possible settings, following the instructions on the README file. I saw on the logs that Postgres encountered the following issue:
postgresql_1 | 2020-12-29 13:53:17.989 UTC [1] LOG: database system is ready to accept connections
postgresql_1 | 2020-12-29 13:53:51.544 UTC [1] LOG: could not fork new process for connection: Resource temporarily unavailable
postgresql_1 | 2020-12-29 13:53:51.562 UTC [1] LOG: could not fork new process for connection: Resource temporarily unavailable
I just did docker-compose up. The problem has obviously to do with resource limitation but what exactly could it be?
Thanks a lot!
Contributor guide
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 the README's simplest Docker Compose setup and compare it with the PostgreSQL log lines showing that new connection processes cannot be forked. Investigate which resource limit could produce this error in the documented setup. Done means identifying the relevant limitation and providing actionable guidance for running the Compose configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql, shell
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100