sameersbn / sameersbn/docker-gitlab
Gitlab CPU Utilization is HIGH due to XMRig tool
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi Team,
We are facing issue regarding GITLAB, (version 13.11.4) CPU is very high due to XMRig tool, we are killing the process but it starts automatically even after killing the process, how can we find the source and fix this issue? what are the possibilities that it can create the issue?
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 examining the Dockerized GitLab deployment and the running XMRig process to determine how it is being launched. Done means identifying the source of the process, explaining the recurrence after termination, and documenting a verified way to prevent it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- infrastructure, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100