Izilungiselelo ze-proxy zezicelo ze-S3 zeregista ye-Distribution

Beka izilungiselelo ze-proxy kunqubo yeregista ye-Distribution efinyelela i-S3, futhi ubale ngokwehlukile amaklayenti adluliselwa endaweni yokugcina izinto.

Kuregista ye-Distribution esebenza ku-container futhi esebenzisa i-HTTP transport eyazi imvelo, dlulisela indlela ye-S3 ku-container yeregista:

services:
  registry:
    environment:
      HTTP_PROXY: http://proxy.example.internal:8080
      HTTPS_PROXY: http://proxy.example.internal:8080
      NO_PROXY: localhost,127.0.0.1

Hlanganisa lokhu ne-image, isitoreji, ukuqinisekisa kanye nama-volumes akhona. Le ngxenye ayilona iregista eliphelele. Igama le-proxy kufanele lifinyeleleke kulelo container, futhi i-scheme kufanele ihambisane nesilaleli se-proxy.

Qinisekisa i-driver ye-S3 kanye nokudluliswa okufakiwe. Umthombo ocashunwe ku-Distribution 2.8.3 usebenzisa isikhathi se-AWS SDK; i-driver noma ukudluliswa okwezifiso kungase kudinge olunye ukucushwa okusekelwayo.

UkuxhumanaUbani ocushayo noma ophenyayo
Iklayenti → iregistaIsilaleli se-HTTP esingenayo seregista kanye nendlela yeklayenti
Daemon → umthombo we-imageIzilungiselelo ze-proxy ze-Docker daemon
Iregista → S3Ukudluliswa kwe-HTTP kwesitoreji kwenqubo yeregista

Ukungena kweklayenti okuphumelelayo kufakazela indlela yokuqala kuphela. I-driver yesitoreji yenza izicelo zayo ku-S3; i-daemon eyadonsa i-image yeregista ngaphambilini ayizenzi lezo zingcingo.

Hlola futhi nokuqondiswa kabusha ngesikhathi sokulandwa kwe-blob. I-Distribution ingaqondisa umsebenzisi endaweni yokugcina izinto, okwenza lelo klayenti lidinge ukufinyelela ngqo ku-S3. Ukucushwa kwe-proxy yeregista akukucushi umsebenzisi. Ukushintsha ukuziphatha kokuqondiswa kabusha kushintsha lapho kugeleza khona ithrafikhi ye-blob, ngakho shono umthumeli nomsebenzi ohlulekayo ngaphambi kokulungisa leso silungiselelo.

Izihloko ezihlobene