Ku shaqaysiinta konteenarrada Docker gadaasha proxy HTTP la xaqiijiyay
Waxaa qoray Kooxda Injineernimada ee ProxyV4 · Updated:
Habaynta proxy ee Docker waxay ku bilaabataa hal su'aal: taraafikadee baa laga rabaa inay dhex marto proxy-ga? Docker wuxuu leeyahay saddex waddo oo kala go'an (app-kaaga xilliga shaqada, docker build, iyo daemon-ka soo jiidaya images-ka), mid walbana wuxuu proxy-giisa ka akhriyaa meel gaar ah. Taas si sax ah u habee, konteenar kasta oo ku yaal hal host wuxuu markaas ku bixi karaa cinwaankiisa gaarka ah ee ProxyV4 IPv4 iyadoo shaxda hagidda ee host-ku aysan waxba iska beddelin.
ENV HTTP_PROXY=http://user:pass@ip:port HTTPS_PROXY=http://user:pass@ip:port- 1 IPUS$1.85
- 3+ IPUS$1.70
- 10+ IPUS$1.60
- 25+ IPUS$1.50
- 50+ IPUS$1.40
- 100+ IPUS$1.30
- 200+ IPUS$1.20
- 500+ IPUS$1.10
- 1 IPUS$1.85
- 3+ IPUS$1.70
- 10+ IPUS$1.60
- 25+ IPUS$1.50
- 50+ IPUS$1.40
- 100+ IPUS$1.30
- 200+ IPUS$1.20
- 500+ IPUS$1.10
Saddex meelood oo Docker uu proxy-ga ka akhriyo
Dejinta doorsoome hal meel waxba uma qabato labada kale. Waxyaabaha inta badan dadka ka yaabiya waxaa ka mid ah in docker pull uu si fiican u shaqeeyo halka app-ka ku dhex jira konteenarku uu wali isticmaalayo IP-ga host-ka laftiisa, ama lidkeeda.
| Taraafikada | Ku habee meeshan | Nuxurka caadiga ah |
|---|---|---|
| App-kaaga ku dhex jira konteenar shaqaynaya | docker run -e HTTP_PROXY=... ama qaybta environment: ee Compose | Codsiyada scraper-ka, wicitaannada API, howlaha automation-ka |
Awaamiirta xilliga docker build | --build-arg HTTP_PROXY=http://user:pass@ip:port | Soo dejinta apt, pip iyo npm ee tillaabooyinka RUN |
| Daemon-ka Docker laftiisa | /etc/systemd/system/docker.service.d/http-proxy.conf | docker pull iyo docker push ee lala xiriiro registries-ka |
Hal IP konteenar kasta
Maadaama doorsoomayaasha xilliga shaqada ay ku nool yihiin deegaanka konteenar kasta, hal VPS wuxuu kicin karaa, tusaale ahaan, toban worker oo mid waliba leeyahay qiime http://user:pass@ip:port oo u gaar ah. Worker kasta wuxuu markaas tusayaa cinwaankiisa bixitaanka boggaga uu booqdo, maadaama ProxyV4 private IPv4 laga kireeyo hal macmiil oo keliya, taraafikada cid kale ma la wadaagto cinwaankaas.
U hay hal fayl oo .env ah adeeg kasta, ama hal adeeg Compose ah proxy kasta, si aad isla markiiba u aragto IP-ga shaqo kasta u gaarka ah. Markaad cusboonaysiiso, waxaad xajisan kartaa isla cinwaannadii hore, markaa waxba kama beddelayso faylashaa.
Doorsoomayaasha xaqiijinaya in stack-gu shaqeeyo
Haddii docker pull uu weli si toos ah u socdo ama container-ku uusan gaari karin database-kiisa isbeddelladan ka dib, bogga proxy-gu ma shaqeynayo wuxuu si taxane ah u dulmarayaa lakab kasta oo Docker ah.
- Qeex magacyada xarfaha waaweyn (
HTTP_PROXY,HTTPS_PROXY,NO_PROXY) iyo kuwa xarfaha yaryar (http_proxy,https_proxy,no_proxy); aaladaha iyo runtimes-ka kala duwan waxay raadiyaan higgaaddo kala duwan - Geli magac kasta oo adeeg Compose ah oo abkaagu waco
NO_PROXY, tusaale ahaanNO_PROXY=localhost,127.0.0.1,redis,postgres, si taraafikada database-ka iyo cache-ku ugu sii jirto shabakadda bridge halkii loo diri lahaa proxy-ga - U isticmaal nidaamka
http://sidoo kaleHTTPS_PROXY; macmiilku wuxuu furayaa CONNECT tunnel goobaha HTTPS-na waxay ahaanayaan kuwo siraysan - Ha ku qorin ereyada sirta ah ee proxy-ga
Dockerfileadoo adeegsanayaENV: waxay ku dambaynayaan lakabyada image-ka. Ka geli xilliga runtime-ka adoo ka keenaya.envama faylka Compose
Tallaabo tallaabo
- 1
U beddel xariiqda dalabka URL proxy ah
Dalabkaaga ProxyV4 wuxuu muujinayaa
ip:port:user:pass; dib ugu qor sidatanhttp://user:pass@ip:port, adoo gacanta ku qoraya ama isticmaalaya proxy format converter. - 2
Ku dar doorsoomayaasha adeegga
Gudaha
docker-compose.yml, qaybta hoose eeenvironment:ee adeegga, ku qeexHTTP_PROXY,HTTPS_PROXY,http_proxy,https_proxyiyoNO_PROXY=localhost,127.0.0.1,redis,db. - 3
Dib u dhis konteenarka
Isbeddelka deegaanku wuxuu saameeyaa kaliya konteenarrada cusub, markaa socodsii
docker compose up -dsi aad dib ugu abuurto adeegga. - 4
Ka hubi IP-ga bixitaanka gudaha
Socodsii
docker exec -it <container> curl -s https://proxyv4.com/api/my-ip. Cinwaanka soo baxa waa inuu noqdaa IP-ga proxy-ga, ee uusan noqon midka host-ka.
Su'aalaha badanaa la isweydiiyo
Ka dib markii aan ku daray HTTP_PROXY app-kaygu ma gaari karo Redis ama Postgres. Maxaa sababay?
Macmiilka HTTP wuxuu hadda codsiyada redis ama db u dirayaa proxy-ga dibadda, kaasoo aan garan karin magacyadaas gudaha ah. Ku qor NO_PROXY (iyo no_proxy), tusaale ahaan NO_PROXY=localhost,127.0.0.1,redis,db, ka dibna dib u samee konteenarka.
Konteenar kasta oo ku yaal hal server ma isticmaali karaa proxy kala duwan?
Haa. Sii adeeg kasta, ama fayl kasta oo .env ah, qiimihiisa gaarka ah ee http://user:pass@ip:port. Konteenarradu waxay wadaagayaan host-ka laakiin internet-ka waxay ku galayaan IP-yo kala duwan.
Maxaa doorsoomayaasha proxy-ga loogu dejinayaa laba jeer, xarfo waaweyn iyo kuwo yaryar?
Ma jiro hal halbeeg oo go'an. Aaladaha ku dhisan libcurl waxay akhriyaan xarfaha yaryar ee http_proxy iyo https_proxy, halka aalado badan oo Go iyo Node ah ay akhriyaan magacyada xarfaha waaweyn. Dejinta labaduba waxay daboolaysaa wax walba oo ku jira image-ka.
docker pull ma isticmaalaa doorsoomayaasha aan ku dejiyay Compose?
Maya. Soo dejinta waxaa sameeya daemon-ka, kaasoo proxy-giisa ka akhriya systemd drop-in /etc/systemd/system/docker.service.d/http-proxy.conf, ee kama akhriyo deegaannada konteenarka.
Ilaha
IPv4 gaar ah oo gooni u ah konteenar kasta
IPv4 gaar ah oo aan xadidnayn oo ku yaal 7 waddan iyo weliba ISP ma guurto ah oo ku yaal US iyo Vietnam, oo si toos ah loo bixiyo bixinta lacagta ka dib. Ma jiro dalab ugu yar.
Fiiri qiimaha tooska ah ee Singapore