sameersbn / sameersbn/docker-gitlab
Very large log files
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello!
I think, gitlab container takes up a lot of disk space.
root@edc9dbd271eb:/var/log/gitlab# du --max-depth=1 -h
1.5G ./nginx
8.8G ./gitlab
286M ./gitlab-shell
735M ./supervisor
12G .
May be exists cron script for cleaning up old logs?
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 container's /var/log/gitlab directories and search the repository for an existing cron or log-cleanup script. Use the reported du output to understand the accumulation, and consider the issue complete when the project’s log-cleanup behavior is identified and the large log growth is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100