I-DNS yensiza ye-Docker kanye nokweqa i-proxy nge-no_proxy

Sebenzisa i-no_proxy ensizeni yangaphakathi ehlosiwe lapho i-HTTP proxy yangaphandle ingakwazi ukuxazulula noma ukufinyelela leyo network.

I-HTTP proxy yangaphandle ayidingi ukwazi igama lensiza ye-Docker api. Ku-http://api:8080/ i-proxy ivula ukuxhumana okulandelayo, ngakho ukusesha okuphumelelayo ngaphakathi kwe-container yohlelo akufakazeli umbono we-DNS we-proxy.

Ukuze uthole ukufinyelela okuqondile okuhlosiwe, engeza okuhlukile endaweni ye-container leyo:

environment:
  http_proxy: http://proxy.example:8080
  https_proxy: http://proxy.example:8080
  no_proxy: api

Izicelo eziqondile ku-api zisebenzisa umzila we-container nesixazululi esingaphakathi. Womabili ama-container asadinga inethiwekhi eyabiwe echazwe umsebenzisi futhi insiza kufanele ilalele ku-8080. Izicelo zangaphandle ezifanelekile zigcina i-proxy. Uma lezo zindawo zomphakathi zingasebenzisa umlamuli womphakathi, uhlu lwe-proxy ye-HTTP luhlinzeka ngabafakazi bama-URL e-proxy angena-akhawunti; gcina i-api phakathi kokuhlukile okuqondile.

Uma ama-container adalwe kabusha egcina okuguquguqukayo okungalindelekile, hlola ingxenye ye-config.json proxies yeklayenti le-Docker, engafaka amanani endawo. Shintsha okufakiwe okuhlosiwe futhi udale kabusha ama-container athintekile ngokugeleza okujwayelekile, ugcina ukucushwa okungahlobene.

Izihloko ezihlobene