sameersbn / sameersbn/docker-gitlab
Gitlab Instance High CPU Utilization due to XMRIG tool
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 in Gitlab instance, as the CPU utilization is very high and the process is xmrig. As there is gitlab-runner running is there any possibility to run this xmrig through gitlab-runner and also
is there any solution to fix this issuse. As the xmrig proccess is running automatically even after killing the process.
Thanks in advance.
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 report concerns a Dockerized GitLab instance, a running GitLab Runner, and an automatically restarting xmrig process. Start by reviewing the container and runner configuration and their logs to determine where the process is launched. Done means identifying the source of the process and documenting a supported fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100