Firewalled / ratelimited when building on docker-hub ?

It appears the repo is firewalling/ ratelimiting hub.docker.com when a custom docker is built.

```
Get:69 http://rpms.litespeedtech.com/debian bionic/main amd64 lsphp74-msgpack amd64 2.0.3-2+bionic [27.7 kB]
Get:70 http://rpms.litespeedtech.com/debian bionic/main amd64 lsphp74-memcached amd64 3.1.5-2+bionic [39.8 kB]
Get:71 http://rpms.litespeedtech.com/debian bionic/main amd64 lsphp74-mysql amd64 7.4.4-1+bionic [44.2 kB]
Get:72 http://rpms.litespeedtech.com/debian bionic/main amd64 lsphp74-sqlite3 amd64 7.4.4-1+bionic [26.9 kB]
W: http://rpms.litespeedtech.com/debian/pool/main/bionic/lsphp74-curl_7.4.4-1+bionic_amd64.deb: Automatically disabled Acquire::http::Pipeline-Depth due to incorrect response from server/proxy. (man 5 apt.conf)
E: Failed to fetch http://rpms.litespeedtech.com/debian/pool/main/bionic/lsphp74-opcache_7.4.4-1+bionic_amd64.deb 400 Bad Request [IP: 34.210.113.18 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Fetched 47.3 MB in 9s (5439 kB/s)
Removing intermediate container a17d0147d48
```

No source files or tests are identified. Start by reproducing the custom Docker build and inspect the apt failure fetching lsphp74-opcache from rpms.litespeedtech.com; done means the build completes without the reported 400 Bad Request or rate-limiting failure.

Written by the indexing model from the issue text.