Tafiyar da kwantenonin Docker a bayan ingantaccen HTTP proxy
Daga Tawagar Injiniyoyi ta ProxyV4 · Updated:
Saitin proxy na Docker yana farawa ne da tambaya guda: wace zirga-zirga ce ya kamata ta fita ta cikin proxy? Docker yana da hanyoyi guda uku daban-daban (manhajarka lokacin aiki, docker build, da kuma manhajar daemon mai janyo hotuna), kuma kowannensu yana karanta proxy dinsa ne daga wuri daban. Idan ka gyara wannan, kowace kwantena a kan uwar garke guda za ta iya fita ta adireshin IPv4 nata na ProxyV4 yayin da teburin routing na uwar garken ke nan ba a taba shi ba.
ENV HTTP_PROXY=http://user:pass@ip:port HTTPS_PROXY=http://user:pass@ip:port- 1 IP$ 1.85
- 3+ IPs$ 1.70
- 10+ IPs$ 1.60
- 25+ IPs$ 1.50
- 50+ IPs$ 1.40
- 100+ IPs$ 1.30
- 200+ IPs$ 1.20
- 500+ IPs$ 1.10
- 1 IP$ 1.85
- 3+ IPs$ 1.70
- 10+ IPs$ 1.60
- 25+ IPs$ 1.50
- 50+ IPs$ 1.40
- 100+ IPs$ 1.30
- 200+ IPs$ 1.20
- 500+ IPs$ 1.10
Wuraren guda uku da Docker ke karanta proxy daga gare su
Saita canjin ma'auni (variable) a wani fanni ba ya aiki ga sauran biyun. Abin mamaki da aka saba gani shi ne docker pull yana aiki alhali manhajar da ke cikin kwantena tana fita ne ta ainihin IP na uwar garken, ko kuma akasin haka.
| Zirga-zirga | Saita shi a | Abubuwan da aka saba gani |
|---|---|---|
| Manhajarka a cikin kwantena mai aiki | docker run -e HTTP_PROXY=... ko sashin environment: a Compose | Bukatar scraper, kiran API, ayyukan sarrafa kansa |
Umarni lokacin docker build | --build-arg HTTP_PROXY=http://user:pass@ip:port | Sauke abubuwan apt, pip da npm a matakan RUN |
| Ainihin Docker daemon | /etc/systemd/system/docker.service.d/http-proxy.conf | docker pull da docker push zuwa rumbunan ajiya (registries) |
IP guda daya ga kowace kwantena
Domin kuwa canje-canjen lokacin aiki suna zama ne a yanayin kowace kwantena, VPS guda daya na iya sarrafa, a ce ma’aikata goma inda kowannensu ke da wata darajar http://user:pass@ip:port daban. Daga nan kowane ma’aikaci yana nuna adireshin fitarsa na kansa ga shafukan da yake ziyarta, kuma tunda adireshin IPv4 na kashin kai na ProxyV4 ana bayar da shi ne ga abokin ciniki guda daya kacal, babu wani zirga-zirgar wani da ke raba wannan adireshin.
Ajiye fayil din .env guda daya ga kowane aiki, ko aikin Compose guda daya ga kowane proxy, domin ka iya ganin ko wane IP ne na kowane aiki a take. Idan ka sabunta biyan kudi, za ka iya rike adiresoshin guda, don haka babu abin da zai canza a cikin wadannan fayilolin.
Sauye-sauyen da ke sa tsarin ci gaba da aiki
Idan har yanzu docker pull yana tafiya kai tsaye ko kuma wani container ya kasa isa ga database dinsa bayan wadannan canje-canje, shafin proxy ba ya aiki yana bi ta kowane layer na Docker a jere.
- Ayana sunayen da ke da manyan haruffa (
HTTP_PROXY,HTTPS_PROXY,NO_PROXY) da kuma masu kananan haruffa (http_proxy,https_proxy,no_proxy); kayan aiki da runtimes daban-daban suna duba rubutu daban-daban ne - Sanya kowane sunan sabis na Compose da manhajar ku ke kira a cikin
NO_PROXY, misaliNO_PROXY=localhost,127.0.0.1,redis,postgres, domin zirga-zirgar bayanan database da cache ta tsaya a hanyar sadarwa ta bridge maimakon a tura ta zuwa proxy - Yi amfani da tsarin
http://donHTTPS_PROXYshi ma; client yana bude ramin CONNECT kuma shafukan HTTPS na ci gaba da kasancewa a boye - Kada ku rubuta kalmomin sirri na proxy a cikin
Dockerfiletare daENV: suna karewa a cikin image layers. Ku sanya su a lokacin gudanarwa daga.envko fayil din Compose
Mataki bayan mataki
- 1
Mayar da layin oda ya zama adireshin URL na proxy
Odarka ta ProxyV4 tana nuna
ip:port:user:pass; sake rubuta shi a matsayinhttp://user:pass@ip:port, da hannu ko kuma tare da proxy format converter. - 2
Sanya canje-canjen a cikin aikin
A cikin
docker-compose.yml, a karkashin sashin aikin naenvironment:, saitaHTTP_PROXY,HTTPS_PROXY,http_proxy,https_proxyda kumaNO_PROXY=localhost,127.0.0.1,redis,db. - 3
Sake kaddamar da kwantena
Canje-canjen yanayi suna aiki ne kawai a kan sabbin kwantenoni, don haka kunna
docker compose up -ddomin sake kaddamar da aikin. - 4
Duba IP na fita daga ciki
Kunna
docker exec -it <container> curl -s https://proxyv4.com/api/my-ip. Adireshin da aka mayar ya kamata ya zama IP na proxy, ba na uwar garken ba.
Tambayoyi da aka fi yi
Bayan saka HTTP_PROXY manhajata ba ta iya samun Redis ko Postgres. Me ya sa?
HTTP client yanzu yana tura bukatun redis ko db zuwa proxy na waje, wanda ba zai iya gano wadannan sunayen na ciki ba. Jera su a cikin NO_PROXY (da kuma no_proxy), misali NO_PROXY=localhost,127.0.0.1,redis,db, sannan ka sake kaddamar da kwantenar.
Shin kowace kwantena a kan uwar garke guda za ta iya amfani da proxy daban?
Eh. Ba wa kowane aiki, ko kowane fayil na .env, darajar http://user:pass@ip:port tasa ta kansa. Kwantenonin suna raba uwar garke daya amma suna fita intanet ta IP daban-daban.
Me ya sa ake saita canje-canjen proxy sau biyu, da manyan da kananan haruffa?
Babu wani tsari guda daya tak. Kayan aikin da aka gina a kan libcurl suna karanta kananan haruffan http_proxy da https_proxy, yayin da yawancin kayan aikin Go da Node ke karanta sunayen da manyan haruffa. Saita su duka biyun yana rufe komai a cikin hoton.
Shin docker pull yana amfani da canje-canjen da na saita a Compose?
A'a. Janyo abubuwa yana gudana ne ta hanyar daemon, wanda ke karanta proxy dinsa daga systemd drop-in /etc/systemd/system/docker.service.d/http-proxy.conf, ba daga yanayin kwantena ba.
Tushe
Kebabben IPv4 na kashin kai ga kowace kwantena
Kebabben IPv4 na kashin kai marar iyaka a kasashe 7 tare da tsayayyen ISP a US da Vietnam, ana bayarwa nan take bayan biyan kudi. Babu mafi karancin oda.
Duba farashin Singapore kai tsaye