sameersbn / sameersbn/docker-gitlab
rancher integration and postgres issue
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I'd like to announce that I ended using your gitlab after having issues with the 'official' gitlab image. You can add it to a rancher instance using this catalog repo:
https://github.com/WebHostingCoopTeam/whc-catalog
I would like to point out that I am having issues with your postgres image, as a workaround I've used the official postgres:9.6-alpine image instead, but I've left the old docker-compose file in place in case it is useful to @sameersbn for debugging (feel free to tell me what I did wrong etc). Cheers! Thanks for the great work Sameer, and I hope you try out rancher with the above catalog.
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
Review the old docker-compose file mentioned in the issue and compare its PostgreSQL setup with the official postgres:9.6-alpine workaround. Inspect the referenced whc-catalog repository for the Rancher integration context. Done means reproducing the PostgreSQL image problem, identifying the configuration cause, and documenting or fixing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgres
- Domain
- databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100