Hi,
I’m using the sonarcloud-scan [1] pipe for bitbucket cloud pipelines, but recently my pipeline has started to die with the following error Service 'docker' exceeded memory limit.
The docker service is limited to 2GB of RAM, and the sonarcloud-scan is the only service there, which means that it is using all the memory available, is this normal that it can grow so big? Can I limit it or control it somehow?
For more details this is the output of top in the docker service container before it’s killed by the oom-killer:
PID VSZ VSZRW RSS (SHR) DIRTY (SHR)^STACK^COMMAND
2866 1765m 1297m 1251m 2588 1216m 0 132 node /opt/atlassian/pipelines/agent/build/.scannerwork/.sonartmp/eslint-bridge-bundle/package/bin/server 43369 127.0.0.1 /opt/atlassian/pipeli
2604 5730m 774m 612m 3232 584m 0 132 /docker-java-home/bin/java -Djava.awt.headless=true -Xmx256m -classpath /opt/sonar-scanner/lib/sonar-scanner-cli-4.6.2.2472.jar -Dscanner.home
43 2973m 356m 70308 4 30188 0 132 dockerd --host=unix:///var/run/docker.sock --host=tcp://0.0.0.0:2375 --authorization-plugin=pipelines --storage-driver=overlay2 --registry-mir
149 1951m 207m 38584 4 10620 0 132 containerd --config /var/run/docker/containerd/containerd.toml --log-level warn
7 696m 43656 10544 548 2936 0 132 pipelines
2535 695m 42736 10732 4 2544 0 132 /usr/local/bin/containerd-shim-runc-v2 -namespace moby -id a6f791a632ae07121717acddb518b53c9f13109b8f51b8fa946c0e3f78476d24 -address /var/run/
2556 19760 464 3364 2040 340 0 132 {run-scanner.sh} /bin/bash /usr/bin/run-scanner.sh
1371 4788 2516 1628 1308 320 0 132 sh
551 4788 2516 1676 1324 320 0 132 sh
751 4736 2464 1584 1328 256 0 132 top
1721 4728 2456 1600 1328 252 0 132 top -m
2605 5940 308 1664 1536 88 0 132 tee /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/sonarsource/sonarcloud-scan/sonarcloud-scan.log