I am trying to run "pack build" (using Paketo as buildpacks provider) in an environment where I do not have direct access to "registry-1.docker.io". Access to the external docker registry is provided via an internal proxy endpoint. When running the command

pack build paketo-demo-app --builder my-dockerhub-proxy.company.com/paketobuildpacks/builder:base

I see that it fails to load the run-image because registry location reverts back to the default. See logs below

base: Pulling from paketobuildpacks/builder
10a039f4d1c5: Pull complete
281985c8fc9f: Pull complete
72ad9888618d: Pull complete
4f4fb700ef54: Pull complete
....
Digest: sha256:07fe9a8fca80c2259062f1400ccc856caa896428d93d5d8c60b6b6fd2480c07e
Status: Downloaded newer image for my-dockerhub-proxy.company.com/paketobuildpacks/builder:base
ERROR: failed to build: invalid run-image 'index.docker.io/paketobuildpacks/run:base-cnb': Error response from daemon: Get https://registry-1.docker.io/v2/: EOF

Is there a Paketo configuration parameter that can override the docker registry location ?