Question for @cujomalainey and @andyross

The (older) IPC fuzzer check added by commit 39551b0 uses the Github Action google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master

This action runs in Docker image gcr.io/oss-fuzz-base/base-builder:latest

Then, the action uses apt-get to download ~ 200 extra Ubuntu packages from http://archive.ubuntu.com/ubuntu on top of oss-fuzz-base/base-builder

One of the main purposes of Docker is to prepackage a complete, specialized image for the job. So it's strange to see that an image named "oss-fuzz-base" is short of 200 Ubuntu packages to... perform fuzzing.

This is not just inefficient; it may also hit some rate limits. If I were http://archive.ubuntu.com/ubuntu , I would not accept that much traffic from Github Actions. In fact this run timed out, http://archive.ubuntu.com/ubuntu
stopped responding: https://github.com/thesofproject/sof/actions/runs/4993519332/jobs/8942765323

To avoid rate limits, most Github Actions download images and packages from internal mirrors like ghcr.io and http://azure.archive.ubuntu.com/

Again it would be even better if the gcr.io/oss-fuzz-base/base-builder:latest image was better self-contained and didn't need that many extra packages in the first place.

EDIT: timing out again in https://github.com/thesofproject/sof/actions/runs/5000127070/jobs/8957163851?pr=7546 / PR #7546