sameersbn / sameersbn/docker-gitlab
error 500 in 14.4.1
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I clone and docker-compose up and it pulls 3 container: redis, postgresql and gitlab:
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ce6663fa08b1 sameersbn/gitlab:14.4.1 "/sbin/entrypoint.sh…" 34 hours ago Up 18 hours (healthy) 443/tcp, 0.0.0.0:10022->22/tcp, :::10022->22/tcp, 0.0.0.0:10080->80/tcp, :::10080->80/tcp docker-gitlab_gitlab_1
77c5f427f878 redis:6.2 "docker-entrypoint.s…" 34 hours ago Up 18 hours 6379/tcp docker-gitlab_redis_1
7c6c9b989f49 sameersbn/postgresql:12-20200524 "/sbin/entrypoint.sh" 34 hours ago Up 18 hours 5432/tcp docker-gitlab_postgresql_1
When I use: http://127.0.0.1:10080 , I prevent to error 500.
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
The issue names docker-compose and the Redis, PostgreSQL, and GitLab containers but no repository file or failing test. Start by checking the compose startup and container logs for the 500 response; done means identifying a reproducible cause and documenting or fixing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, postgresql, redis
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100