x/build: ppc64le builders missing curl

[prattmic]

I am creating new race sysos for #78059 and the racebuild script requires curl on the builder. Unfortunately gotip-linux-ppc64le_power8, gotip-linux-ppc64le_power9, and gotip-linux-ppc64le_power10 gomotes are all missing curl.

Could we add curl? Oddly, https://cs.opensource.google/go/x/build/+/master:env/linux-ppc64le/osuosl/Dockerfile;bpv=1 does seem to list curl. Is that not used anymore?

For now I will skip updating the ppc64le race sysos.

cc @golang/ppc64

[mkumatag]

@pmur @jkrishmys ^^

[jkrishmys]

Hi @prattmic, thanks for flagging this. I will take a look at the ppc64le gomote environments (P8/P9/P10) and follow up with details.

[jkrishmys]

I manually checked the OSU Power8, Power9, and Power10 hosts (both ppc64le and ppc64), and curl is present on the host OS across all of them (e.g., 7.68.0 on P9LE, 8.5.0 on P10LE). So the discrepancy appears to be between the host and the gomote/buildlet environment. I attempted to verify this directly, but I’m currently hitting a 403 on gomote create, so I’m unable to check inside those instances myself.

[cagedmantis]

@jkrishmys Are you using the latest version of gomote?

[jkrishmys]

@jkrishmys Are you using the latest version of gomote?

I have updated to the latest version, but I’m still hitting a 403 on gomote create.

For context, gomote login succeeds with my Google account, but the create command still fails. I’m able to authenticate, but I may not have access to create those builder instances.

[pmur]

@jkrishmys did you verify the CI containers have curl? I think gomote runs within the CI container.

If it's missing, you'll need to update the CI container image, that shouldn't be too difficult. I think the breadcrumbs (the dockerfile) to recreate the images.

It's also good practice to refresh those every release or so. A reminder, the ppc64le power8 builders are stuck on ubuntu 20.04; it's the last to support power8.

[jkrishmys]

@pmur, I verified this directly on the OSU ppc64le Power10 builder host. The host OS has curl, but the running golang/luci-builder CI container does not: /usr/bin/curl is absent, curl is not installed, and apt shows it is available.
I’m planning to fix this by updating the ppc64le CI image path used by rundockerluci / golang/luci-builder so that curl is present in the live builder container, then refreshing the deployed image.

[jkrishmys]

@pmur Thanks, as you suggested, I checked on the OSU ppc64le Power10 host and found that the builders are using a locally maintained image under ~/luci-docker — that was spot on.

The local Dockerfile there did not include curl, which explains why the live golang/luci-builder containers were missing it even though the host had curl installed. I updated the local Dockerfile to include curl, rebuilt the golang/luci-builder image, removed the existing containers, and restarted rundockerluci so they were recreated from the new image.

Verified across all 4 running builder instances that:

/usr/bin/curl is present
curl --version works

So this is now fixed on the ppc64le Power10 builder. I’ll take a look at the Power9 and Power8 builders as well to make sure they’re consistent.