Ukusebenzisa ama-container e-Docker ngemuva kwe-proxy ye-HTTP efakazelwe
Ibhalwe yiThimba Lonjiniyela lakwa-ProxyV4 · Updated:
Ukusetha i-proxy ye-Docker kuqala ngombuzo owodwa: iyiphi i-traffic okufanele iphume nge-proxy? I-Docker inezindlela ezintathu ezihlukene (uhlelo lwakho ngenkathi lusebenza, docker build, kanye ne-daemon edonsa izithombe), futhi ngayinye ifunda i-proxy yayo endaweni ehlukile. Kulungise lokho futhi wonke ama-container kuseva eyodwa angaphuma ngekheli lawo le-IPv4 le-ProxyV4 kuyilapho ithebula lomzila leseva lingathintwa.
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
Izindawo ezintathu lapho i-Docker ifunda khona i-proxy
Ukusetha i-variable kusikophu esisodwa akwenzi lutho kokunye okubili. Into evame ukumangaza ukusebenza kwe-docker pull kuyilapho uhlelo olungaphakathi kwe-container lusalokhu luphuma nge-IP yeseva uqobo, noma okuphambene nalokho.
| I-traffic | Yimise ku- | Okuqukethwe okuvamile |
|---|---|---|
| Uhlelo lwakho olungaphakathi kwe-container esebenzayo | docker run -e HTTP_PROXY=... noma ibhulokhi le-environment: ku-Compose | Izicelo ze-scraper, izingcingo ze-API, imisebenzi ye-automation |
Imiyalo ngesikhathi se-docker build | --build-arg HTTP_PROXY=http://user:pass@ip:port | Ukulanda kwe-apt, pip kanye ne-npm ezinyathelweni ze-RUN |
| I-daemon ye-Docker uqobo | /etc/systemd/system/docker.service.d/http-proxy.conf | docker pull kanye ne-docker push kuma-registry |
I-IP eyodwa nge-container ngayinye
Ngenxa yokuthi ama-variable okusebenza ahlala endaweni ye-container ngayinye, i-VPS eyodwa ingasebenzisa, ake sithi, izisebenzi eziyishumi lapho ngayinye inenani le-http://user:pass@ip:port elihlukile. Isisebenzi ngasinye sibe sesibonisa ikheli laso lokuphuma kumasayithi asivakashelayo, futhi njengoba i-IPv4 eyimfihlo ye-ProxyV4 iqashiswa ikhasimende elilodwa kuphela, ayikho i-traffic yomunye umuntu eyabelana ngalelo kheli.
Gcina ifayela elilodwa le-.env kusevisi ngayinye, noma isevisi eyodwa ye-Compose nge-proxy ngayinye, ukuze ukwazi ukubona ngokushesha ukuthi iyiphi i-IP engaphansi kowuphi umsebenzi. Lapho uvuselela, ungagcina amakheli afanayo, ngakho akukho lutho kulawo mafayela okufanele lushintshe.
Ama-variable agcina isitaki sisebenza
Uma docker pull isaqonda ngqo noma isiqukathi singakwazi ukufinyelela i-database yaso ngemuva kwalezi zinguquko, ikhasi elithi i-proxy engasebenzi lichaza isendlalelo ngasinye se-Docker ngokulandelana.
- Chaza amagama anezinhlamvu ezinkulu (
HTTP_PROXY,HTTPS_PROXY,NO_PROXY) kanye nalawo anezinhlamvu ezincane (http_proxy,https_proxy,no_proxy); amathuluzi ahlukene nama-runtime abheka izipelingi ezahlukene - Faka wonke amagama amasevisi e-Compose abizwa uhlelo lwakho ku-
NO_PROXY, isiboneloNO_PROXY=localhost,127.0.0.1,redis,postgres, ukuze ithrafikhi ye-database neye-cache ihlale kunethiwekhi ye-bridge kunokuba ithunyelwe ku-proxy - Sebenzisa i-scheme se-
http://naku-HTTPS_PROXYfuthi; iklayenti livula umhubhe we-CONNECT kanti izingosi ze-HTTPS zihlala zibethelwe - Ungabhali amaphasiwedi e-proxy ku-
Dockerfileusebenzisa i-ENV: agcina esezezingqimbeni ze-image. Wafake ngesikhathi sokusebenza kusuka ku-.envnoma efayeleni le-Compose
Isinyathelo ngesinyathelo
- 1
Guqula ulayini we-oda ube yi-URL ye-proxy
I-oda lakho le-ProxyV4 libala
ip:port:user:pass; libhale kabusha njenge-http://user:pass@ip:port, ngesandla noma nge-proxy format converter. - 2
Engeza ama-variable kusevisi
Ku-
docker-compose.yml, ngaphansi kwe-environment:yesevisi, sethaHTTP_PROXY,HTTPS_PROXY,http_proxy,https_proxykanye ne-NO_PROXY=localhost,127.0.0.1,redis,db. - 3
Dala kabusha i-container
Izinguquko zendawo zisebenza kuphela kuma-container amasha, ngakho sebenzisa
docker compose up -dukudala kabusha isevisi. - 4
Hlola i-IP yokuphuma ngaphakathi
Sebenzisa
docker exec -it <container> curl -s https://proxyv4.com/api/my-ip. Ikheli elibuyisiwe kufanele libe yi-IP ye-proxy, hhayi eyeseva.
Imibuzo evame ukubuzwa
Ngemuva kokwengeza i-HTTP_PROXY uhlelo lwami alukwazi ukufinyelela ku-Redis noma i-Postgres. Kungani?
Iklayenti le-HTTP manje selithumela izicelo ze-redis noma db ku-proxy yangaphandle, engakwazi ukuxazulula lawo magama angaphakathi. Wabale ku-NO_PROXY (kanye naku-no_proxy), isib. NO_PROXY=localhost,127.0.0.1,redis,db, bese udala kabusha i-container.
Ingabe i-container ngayinye kuseva eyodwa ingasebenzisa i-proxy ehlukile?
Yebo. Nikeza isevisi ngayinye, noma ifayela ngalinye le-.env, inani layo le-http://user:pass@ip:port. Ama-container abelana ngeseva kodwa aphuma ku-inthanethi ngama-IP ahlukene.
Kungani usetha ama-variable e-proxy kabili, ngezinhlamvu ezinkulu nezincane?
Alikho izinga elilodwa. Amathuluzi akhelwe phezu kwe-libcurl afunda http_proxy kanye ne-https_proxy enezinhlamvu ezincane, kuyilapho amathuluzi amaningi e-Go ne-Node efunda amagama anezinhlamvu ezinkulu. Ukusetha kokubili kuhlanganisa konke okusesithombeni.
Ingabe i-docker pull isebenzisa ama-variable engiwasethe ku-Compose?
Cha. Ukudonsa kwenziwa yi-daemon, efunda i-proxy yayo kusuka ku-drop-in ye-systemd /etc/systemd/system/docker.service.d/http-proxy.conf, hhayi ezindaweni zama-container.
Imithombo
I-IPv4 ehlukile eyimfihlo ye-container ngayinye
I-IPv4 eyimfihlo engalinganiselwe emazweni angu-7 kanye ne-ISP emile e-US nase-Vietnam, enikezwa ngokuzenzakalelayo ngemuva kokukhokha. Akukho i-oda eliphansi.
Bheka izintengo ezibukhoma zase-Singapore