env/linux-ppc64le/osuosl: increase container ram limits

We are hitting resource limit during the API tests which is causing
consistent failures.

These VM's claim to have 20G ram allocated and run to up to 5 builders.
This will potentially overcommit them, but I suspect some amount of that
usage is shared.

Likewise, remove specific number from ppc64 builders in the
event we need change this number again.

Fixes golang/go#44541

Change-Id: Ifad1aeb9f461d59151d569d878d94d93cb426351
Reviewed-on: https://go-review.googlesource.com/c/build/+/296669
Reviewed-by: Dmitri Shuralyov <[email protected]>
Trust: Lynn Boger <[email protected]>

Author: pmur

env/linux-ppc64/osuosl/rundockerbuildlet.service

@@ -9,7 +9,7 @@ WantedBy=network-online.target
 Type=simple
 # The (-n * -cpu) values must currently be <= number of host cores.
 # The host has 10 cores, so the -n=5 (five containers) * -cpu=2 (two CPUs per container) == 10.
-# TODO: add -memory=3.9g once the docker/crun issues are fixed to support memory limits.
+# TODO: Use -memory option once the docker/crun issues are fixed to support memory limits.
 ExecStart=/usr/local/bin/rundockerbuildlet -basename=ppc64_ -image=golang/builder -n=5 -cpu=2 -memory= --env=host-linux-ppc64-osu
 Restart=always
 RestartSec=2

env/linux-ppc64le/osuosl/rundockerbuildlet.service

@@ -9,7 +9,7 @@ WantedBy=network-online.target
 Type=simple
 # The (-n * -cpu) values must currently be <= number of host cores.
 # The host has 10 cores, so the -n=5 (five containers) * -cpu=2 (two CPUs per container) == 10.
-ExecStart=/usr/local/bin/rundockerbuildlet -basename=power_ -image=golang/builder -n=5 -cpu=2 -memory=3.9g --env=XXX
+ExecStart=/usr/local/bin/rundockerbuildlet -basename=power_ -image=golang/builder -n=5 -cpu=2 -memory=4.9g --env=XXX
 Restart=always
 RestartSec=2
 StartLimitInterval=0