docker pull ta VPN: daemon yana da nata cibiyar sadarwa

Kwamfutar tafi-da-gidanka tana kan VPN na kamfani, curl yana isa registry ta ciki, amma duk da haka docker pull yana mutuwa da EOF. Wannan haɗuwa ba sabani ba ce. Umurnin da kuka rubuta yana gudana a cikin shell ɗinku, amma canja wurin yana gudana a cikin daemon ɗin da Docker CLI ya zaɓa, kuma wannan daemon na iya kasancewa a wata mashin gaba ɗaya. Hanyar cibiyar sadarwar sa ce dole ta yi aiki, kuma saitunan proxy ɗinsa ne suka dace.

Fara da gano injin, ba hanya ba

Gudanar da docker context show da docker version. Fitarwar sigar tana buga sashe na abokin ciniki da sashe na uwar garke, kuma shingen uwar garke yana gaya muku wanda ya amsa: injin na gida, na'urar kama-da-wane ta Docker Desktop, ko daemon a wata na'ura mai nisa. docker context inspect zai nuna ƙarshen yanayin da aka zaɓa idan kuna son tabbatarwa, kuma babu ɗaya daga cikin waɗannan umarnin da ke canza komai.

Sauya yanayi kamar DOCKER_HOST na iya nuni da CLI a hankali zuwa wani injin daban da wanda kuke tsammani, wanda shine bayanin da aka saba yi game da kwamfutar tafi-da-gidanka da ake ganin tana kan VPN yayin da ja-in ya tafi wani wuri.

Daemon yana da nasa asalin cibiyar sadarwa

Injin mai nisa yana buƙatar nasa hanyar da aka amince da ita zuwa registry mai zaman kansa. Haɗa abokin ciniki na VPN na kwamfutar tafi-da-gidanka yana ba wannan kwamfutar hanya; ba ya ba daemon da ke cikin dakin gwaji ko yankin gajimare irin wannan adireshin mai zaman kansa. Idan injin Docker Desktop ne, ja-in yana faruwa a cikin na'urar kama-da-wane ta sa, wadda ke da nata tsarin cibiyar sadarwa da na proxy daban daga yanayin shell ɗinku.

Shi ya sa nasarar curl a kan mashin shaida ce game da mashin kawai, ba wani abu ba.

Gano wace musayar registry ce ta ƙare

Ja-in hoto jerin abu ne: tabbatarwa, samun manifest, sannan canja wurin blob waɗanda galibi ana tura su zuwa ajiyar abu ko ƙarshen CDN. Nasarar docker login tana tabbatar da mataki na farko kawai, kuma alama na iya zama cikakkiyar inganci yayin da masaukinta na blob da aka tura ba ya isa daga cibiyar sadarwar daemon. Rubuta ainihin lokacin, maganar hoto da farkon abin da ya faru mai amfani daga log ɗin daemon ko abokin ciniki kafin ku canza wani abu.

EOF shi kaɗai baya ambaton wani dalili. Yana iya zama haɗin da ya yanke, proxy da ya watsar da rafi, ƙarewar lokaci ko matsalar MTU, kuma yin hasashe a tsakaninsu ba tare da abin da ya faru mai tambarin lokaci ba shine yadda mutane ke sake gina injin lafiyayye. Dauki matsirin byte a fitarwar abokin ciniki a matsayin bayanai, domin canja wurin da ke tsayawa a girman ɗaya kowace lokaci dabba ce ta daban da wanda baya farawa. Rubuta duka sakamakon biyu kuma kwatanta su a tsakanin yunƙuri.

Saita sashin da ke canja wuri

Don injin Linux na asali, proxy yana cikin yanayin sabis ɗin, ba cikin shell ɗinku ba. Fayil ɗin drop-in a ƙarƙashin /etc/systemd/system/docker.service.d/ tare da shigarwar HTTP_PROXY, HTTPS_PROXY da NO_PROXY, sannan systemctl daemon-reload da sake farawa, shine tsarin da aka rubuta. Docker Desktop yana bayar da waɗannan ƙima ta hanyar saitunansa, kuma gyara bayanin shell baya taɓa ko ɗaya daga cikinsu.

Idan ya kamata a isa registry kai tsaye ta VPN, daemon yana buƙatar mai warwarewa, hanya da kau da proxy da gangan, ba kau da shi kawai ba. Daidaita NO_PROXY kwatancen zare ne ga kowane sashi, kuma keɓancewa ba tare da hanyar da ke ƙasa ba yana haifar da gazawa da ke kama da matsalar proxy.

Lokacin da binciken TLS na kamfani ke kan hanyar da aka amince da ita, girka tushensa da aka tabbatar ta hanyar aikin injin ko Desktop. Ƙara registry cikin insecure-registries wani canji ne daban wanda ke kashe tabbatarwa, kuma ba tsarin ajiyar amana ba ne.

Maimaita ja-in da aka sarrafa kuma duba abin da ya canza

Canza iyaka ɗaya, sake farawa sashin da ya mallaki ta, sannan maimaita irin wannan ja-in daga irin wannan yanayi. Tabbatar da maganar hoton da digest da aka samu, ba rashin kuskure ba, domin Layer da aka ajiye a cache na iya sa yunƙuri na biyu ya bi ƙaramin ɓangare na hanya fiye da na farko. Ajiye canja wurin da suka faru a cikin tikitin, domin su ne kawai rikodin abin da sake yunƙurin ya gwada da gaske.

Matakan build da kwantena masu gudana suna da nasu yanayin cibiyar sadarwa, don haka ɗauke su a matsayin tambayoyi daban bayan ja-in da kansa ya yi aiki.