Ithuluzi lokwakha lingaxazulula ukuncika kwalo ngempumelelo, kodwa i-Paketo buildpack ayikwazi ukulanda i-runtime. I-buildpack isebenza ngaphakathi kwe-container ye-builder futhi idinga ukufakwa kwayo kwe-proxy.

Umsebenzi we-bootBuildImage we-Gradle

Ku-Groovy build.gradle enomsebenzi we-bootBuildImage okhona we-Spring Boot:

tasks.named("bootBuildImage") {
    environment["HTTP_PROXY"] = "http://proxy.example:8080"
    environment["HTTPS_PROXY"] = "http://proxy.example:8080"
}

I-plugin ye-Maven isebenzisa i-image.env

Ku-spring-boot:build-image, beka la mavelu ngaphansi kwe-image.env ekulungiseni okukhona kwe-plugin ye-Spring Boot Maven:

<configuration>
  <image>
    <env>
      <HTTP_PROXY>http://proxy.example:8080</HTTP_PROXY>
      <HTTPS_PROXY>http://proxy.example:8080</HTTPS_PROXY>
    </env>
  </image>
</configuration>

Kokubili imvelo yomsebenzi we-Gradle kanye ne-image.env ye-Maven kunikeza i-builder amavelu. Womabili amagama angakhomba umlamleli we-HTTP ojwayelekile, kuhlanganise nama-URL e-artefact e-HTTPS. Ekulandeni kwama-artefact omphakathi okuvunyelwe nge-proxy yomphakathi, uhlu lwe-proxy ye-HTTP lunikeza abazongenela phansi kula mavelu e-builder.

Lokhu kulungisa akuncikile ezimisweni ze-systemProp.http.proxyHost ze-Gradle. Lezo ze-JVM futhi azilungisi enye inqubo ngokuzenzakalela ku-builder.

I-Docker daemon kufanele iqale ithole izithombe ze-builder ne-run ezidingekayo. Ukuhluleka kwe-registry kuleso sigaba sangaphambili kudinga umzila nokulungiswa kwe-registry ye-daemon, hhayi okuguqukayo okunikezwa i-buildpack engakaqali.

Sebenzisa indawo yokugcina ye-proxy efikelelekayo kusuka ku-container ye-builder. Ikheli layo le-loopback likhomba leyo container, hhayi ngempela isiteshi somsebenzi somthuthukisi.

Gcina nemvelo yokusebenza yohlelo lokusebenza lokugcina inenjongo. Ukufinyelela ngesikhathi sokwakha nomzila osetshenziswa lapho uhlelo lusebenza kamuva kuyizinqumo ezimbili zokulungisa ezihlukene.

Izihloko ezihlobene