DNS na sabis ɗin Docker da ketare wakili da no_proxy

Yi amfani da no_proxy don sabis na ciki da aka nufa lokacin da wakilin HTTP na waje ba zai iya warware ko isa wannan hanyar sadarwa ba.

Wakilin HTTP na waje bai buƙatar sanin sunan sabis ɗin api na Docker ba. Don http://api:8080/ wakilin yana buɗe haɗin gaba, don haka nasarar bincike a cikin kwandon aikace-aikacen ba ta tabbatar da ra'ayin DNS na wakilin ba.

Don shiga kai tsaye da aka nufa, ƙara keɓancewar zuwa yanayin wannan kwandon:

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

Buƙatun kai tsaye zuwa api suna amfani da hanyar kwandon da mai warwarewar da ke ciki. Kwanonin biyu har yanzu suna buƙatar hanyar sadarwar da mai amfani ya ayyana kuma sabis ɗin dole ne ya saurara a 8080. Buƙatun waje da suka cancanta suna riƙe wakilin. Idan waɗannan wuraren jama'a na iya amfani da mai shiga tsakani na jama'a, jerin wakilan HTTP yana ba da 'yan takara don URL ɗin wakili marasa asusu; riƙe api cikin keɓancewar kai tsaye.

Idan kwandon da aka sake ƙirƙira suna riƙe da masu canji da ba a zata ba, duba sashen config.json proxies na abokin ciniki na Docker, wanda zai iya shigar da ƙimar yanayi. Canza shigarwar da aka nufa kuma sake ƙirƙirar kwandon da abin ya shafa ta hanyar al'ada, tare da kiyaye tsarin da ba shi da alaƙa.

Labarai masu alaƙa