Yadda ake saita proxy a Docker (Kwantena, Compose da Builds)
Updated:
Lokacin gudanar da scrapers masu kwantena da yawa, ma'aikatan sarrafa kansa, ko kumburan DePIN a kan uwar garke guda, shigar da sauye-sauyen muhalli na HTTP_PROXY da HTTPS_PROXY ga kowace kwantena yana ba kowane sabis damar fita ta keɓaɓɓen adireshin IPv4 na dindindin nasa daga VinaProxy ba tare da sauya teburin routing na babbar na'urar ba.
ENV HTTP_PROXY=http://user:pass@ip:port HTTPS_PROXY=http://user:pass@ip:port- IP 1₫ 40,000
- IPs 5+₫ 35,000
- IPs 10+₫ 25,000
- IPs 20+₫ 25,000
- IPs 50+₫ 25,000
- IPs 100+₫ 25,000
- IPs 200+₫ 25,000
- IPs 500+₫ 25,000
- IPs 1000+₫ 22,000
- IPs 2000+₫ 20,000
- IP 1₫ 40,000
- IPs 5+₫ 35,000
- IPs 10+₫ 25,000
- IPs 20+₫ 25,000
- IPs 50+₫ 25,000
- IPs 100+₫ 25,000
- IPs 200+₫ 25,000
- IPs 500+₫ 25,000
- IPs 1000+₫ 22,000
- IPs 2000+₫ 20,000
Fahimtar fannoni 3 na saitin proxy a Docker
Docker yana raba zirga-zirgar lokacin aikin kwantena, zirga-zirgar ginin hoto, da jawo rajista na daemon:
| Fannin Docker | Inda Ake Saitawa | Abin da Yake Turawa |
|---|---|---|
| 1. Lokacin Aikin Kwantena | docker run -e HTTP_PROXY=... ko Compose environment: | Zirga-zirgar da manhaja ke samarwa a cikin wannan takamaiman kwantena |
2. Ginin Hoto (docker build) | --build-arg HTTP_PROXY=http://user:pass@ip:port | Sauke kunshin sarrafa abubuwa (apt, pip, npm) yayin gini |
3. Docker Daemon (dockerd) | /etc/systemd/system/docker.service.d/http-proxy.conf | Bukatu na docker pull da docker push zuwa rajista |
Mafi kyawun ayyuka na Docker Compose da dokokin NO_PROXY
- Saita duka manyan haruffa (
HTTP_PROXY,HTTPS_PROXY,NO_PROXY) da kananan haruffa (http_proxy,https_proxy,no_proxy) domin dukkan kayan aikin Linux CLI da runtimes na harsuna su gane su - Koyaushe lissafa sunayen sabis na ciki na Docker Compose (misali,
NO_PROXY=localhost,127.0.0.1,redis,postgres) domin zirga-zirgar tsakanin kwantena ta tsaya a kan hanyar sadarwa ta bridge ta gida - Kada a taba sanya kalmomin sirri na proxy a cikin hotunan jama'a tare da
ENVa cikinDockerfile—shigar da su a lokacin aiki ta hanyar.envkodocker-compose.yml
Mataki-mataki
- 1
Tsara proxy dinka a matsayin http://user:pass@ip:port
Sauya layin VinaProxy
ip:port:user:passdinka ta amfani da Proxy Format Converter dinmu. - 2
Sanya sauye-sauyen muhalli a cikin docker-compose.yml
A karkashin
environment:na sabis dinka, ayyanaHTTP_PROXY,HTTPS_PROXY,http_proxy,https_proxy, daNO_PROXY=localhost,127.0.0.1,redis,db. - 3
Fara ko sake kirkirar kwantena
Gudanar da
docker compose up -ddomin aiwatar da sauye-sauyen muhallin. - 4
Tabbatar da IP na fita daga cikin kwantena
Gudanar da
docker exec -it <container> curl -s https://vinaproxy.com/api/my-ipdomin tabbatar da cewa kwantenar na fita ta hanyar IP na proxy dinka.
Tambayoyin da aka fi yi
Me ya sa kwantena ta ba za ta iya isa ga kwantena ta ta Redis ko Postgres ba bayan saita HTTP_PROXY?
Idan babu NO_PROXY, abokin ciniki na HTTP dinka zai yi kokarin isa ga sunayen sabis na ciki kamar redis ko db ta hanyar proxy na waje. Sanya NO_PROXY=localhost,127.0.0.1,redis,db (da kananan haruffa no_proxy) domin kauce wa proxy ga rundunonin bridge na ciki.
Zan iya ware proxies 20 mabanbanta ga kwantenoni 20 a kan VPS guda daya?
Eh. Ayyana kowane sabis na kwantena (ko tura sauye-sauyen .env mabanbanta) tare da zaren http://user:pass@ip:port nasa na kansa.
Me ya sa ake saita sauye-sauyen proxy na manyan da kananan haruffa?
Wasu dakunan karatu na Linux (kamar libcurl) suna fara duba kananan haruffa http_proxy / https_proxy, yayin da kayan aikin Go da Node galibi suke duba manyan haruffa HTTP_PROXY / HTTPS_PROXY.
Bada keɓaɓɓun IP masu tsayawa ga kowace kwantenar Docker
Keɓaɓɓun IPv4 marasa iyaka da kuma Static ISP proxies nan take a fadin kasashe 7.
Sayi Docker Proxies