Setting Proxy for docker during maven spring boot build

[tiagodj]

Hi.

I am trying to setup proxy to be used during build. I am building it using maven and the spring-boot-maven-plugin, using paketobuildpacks/builder-jammy-base.

This runs in gitlab, using an image based on the official docker:20.10.22 image.

I have the following configuration:

<plugin>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-maven-plugin</artifactId>
    <executions>
        <execution>
            <id>build-image</id>
            <phase>install</phase>
            <goals>
                <goal>build-image-no-fork</goal>
            </goals>
            <configuration>
                <image>
                    <builder>paketobuildpacks/builder-jammy-base</builder>
                    <name>${image.repository}/${image.name}:${image.version}</name>
                    <createdDate>now</createdDate>
                    <env>
                        <BP_JVM_VERSION>${java.version}</BP_JVM_VERSION>
                        <HTTP_PROXY>${proxy.http}</HTTP_PROXY>
                        <HTTPS_PROXY>${proxy.https}</HTTPS_PROXY>
                    </env>
                </image>
            </configuration>
        </execution>
    </executions>
</plugin>

I am not sure the proxy configuration is being picked up, though.

During build I see these logs:

25481 [INFO] 
25482 [INFO] --- spring-boot-maven-plugin:3.2.0:build-image-no-fork (build-image) @ topology-adapter ---
26471 [INFO] Building image 'docker.io/my/image-name:1234'
26471 [INFO] 
28691 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 0%
30719 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 1%
32769 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 3%
34770 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 4%
36776 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 5%
...
306071 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 95%
306170 [INFO]  > Pulling builder image 'docker.io/paketobuildpacks/builder-jammy-base:latest' 100%
306170 [INFO]  > Pulled builder image 'paketobuildpacks/builder-jammy-base@sha256:90f84feaeedaa46c39aff145ed21df0ee47c0a456adb5ad6097b3af9b7a02f8c'

You can see that this download takes a long time, which makes me suspect that it's not being pulled through the proxy.

For comparison, there's this other download:

337011 [INFO]     [creator]       BellSoft Liberica JRE 17.0.10: Contributing to layer
337011 [INFO]     [creator]         Downloading from https://github.com/bell-sw/Liberica/releases/download/17.0.10+13/bellsoft-jre17.0.10+13-linux-amd64.tar.gz
343671 [INFO]     [creator]         Verifying checksum

Which seems to be pulled through the proxy, because it runs reasonably fast.

So my question is: how can I verify that the download of builder-jammy-base goes through the proxy as well?

Thanks.