sameersbn / sameersbn/docker-gitlab
Gitlab constantly uploads stuff, even if it's not in use
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello guys :)
I don't think it's a bug, but mostly a fishy behaviour I would like to highlight/get clarifications about :)
A couple of months ago I installed this Docker image on my QNAP nas, in order to have a local-only copy of Gitlab to use as git service for my own projects. Modern QNAP nas devices run Docker, so the user can expand their functionality running several containers on the top of them.
The three containers (gitlab, postgressql, redis) worked fine, but I noticed that the former one was CONSTANTLY talking with the internet and uploading stuff. I monitored this behaviour for MONTHS, no breaks, a constant uploading. The "funny" thing is that I rarely use it, that there is just one user (me) and no access from the outside is granted.
What Gitlab is uploading all the time, even if nobody is using it?
I attach a screenshot.
Thanks!
Rubèn

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 by identifying which of the GitLab, PostgreSQL, or Redis containers is responsible for the constant upload, then inspect the container's outbound connections and available logs. Done means documenting what is being uploaded, whether the activity is expected, and any relevant configuration or mitigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100