Indlela yokuhlanganisa i-Docker, i-Traefik, ne-Portainer njengesitaki esiphelele

Informatec Digital » Izinsiza » Indlela yokuhlanganisa i-Docker, i-Traefik, ne-Portainer njengesitaki esiphelele

Ukusetha i-stack yesimanje nge -Docker, i-Traefik, ne-Portainer okwamanje kungenye yezindlela ezilula zokuphatha izitsha kuseva eyodwa nokuveza izinsizakalo eziningi nge-HTTPS ngaphandle kokuvinjelwa ekucushweni. Ubuhle bakho ukuthi i-Traefik isebenza njengommeleli oguquguqukayo oguquguqukayo, kuyilapho i-Portainer inikeza isikhombimsebenzisi sewebhu esilula kakhulu sokuphatha i-Docker, futhi uma ufuna, ne-Swarm.

Kulesi sihloko uzobona ukuthi kanjani ukufaka iTraefik njengommeleli ophambene phambi kukaPortainer Kokubili esimweni "se-classic" Docker (ezimele) kanye neqembu le-Docker Swarm, indlela yokuhlanganisa i-TLS (esayinwe ngumuntu noma i-Let's Encrypt), kanye nokuthi yimaphi amafayela okucushwa asebenzayo (traefik.yml, dynamic.yml y docker-compose.yml) kanye namaqhinga avamile nge-middleware, amanethiwekhi kanye nezinkinga ezivamile zokumaka ku-Traefik.

Yiziphi izindima uDocker, uTraefik, noPortainer abanazo ekwakhiweni kwezakhiwo?

Kulolu hlobo lokusetha, i-Docker iyisendlalelo esiyisisekelo lapho izitsha zisebenza khona, i-Traefik isebenza njenge-proxy ebuyela emuva kanye ne-load balancer ethola zonke izicelo ze-HTTP/HTTPS kumachweba angu-80 no-443 bese izithumela esitsheni esifanele, kanti i-Portainer inikeza isikhombimsebenzisi esibonakalayo sokuphatha izithombe, izitsha, amavolumu, amanethiwekhi, kanye nezitaki ze-Docker noma ze-Swarm.

Umqondo uwukuba nomphathi oyedwa one-Docker lapho I-Traefik itholakala “esangweni”: lalela ezindaweni zokungena web (80) futhi websecure (443), ixazulula izitifiketi ze-TLS (ngokuvamile nge-Let's Encrypt) futhi, ngenxa yokuhlanganiswa nomhlinzeki we-Docker, ithola ngokuzenzakalelayo izinsizakalo ozivezayo ngokungeza amalebula ezitsheni.

Ngakolunye uhlangothi, iPortainer isebenza njengesitsha nje, kodwa ivezwe ngaphandle isizinda esincane esithile, isibonelo portainer.tudominio.com, ivikelwe yi-TLS futhi, uma kufiswa, ngemuva kwe-middleware eyengeziwe yokuqinisekisa ngale kokungena ngemvume kukaPortainer. Konke lokhu kuhlelwe nge docker-compose okuchaza iTraefik, iPortainer kanye nenethiwekhi evamile yohlobo proxy.

Inzuzo ecacile yale ndlela ukuthi ungathumela izinsizakalo ezintsha ngokumane ungeze amalebula ezitsheni zakho: I-Traefik ibona ushintsho ku-Docker, idale ama-router, izinsizakalo, kanye ne-middleware ngokushesha, futhi ngemizuzwana nje unesizinda esisha noma umzila oqalayo futhi osebenzayo ngaphandle kokuthinta ngesandla amafayela wokucushwa okungaguquki.

Ukucushwa kwe-Traefik okumile: traefik.yml

Ukucushwa kwe-static kweTraefik kuvame ukugcinwa kufayela elifana neli traefik.ymlefakwe ngaphakathi kwesitsha. Lapha kuchazwa ideshibhodi, izindawo zokungena, abahlinzeki, kanye nesixazululi sesitifiketi Ake sibhale nge-Encrypt, phakathi kwezinye izinto.

Ukucushwa kwe-YAML okuvamile kuqala ngokusebenzisa i-API kanye nephaneli yokulawula ngento efana nalokhu api: dashboard: trueLokhu kuvumela ukufinyelela ku-interface yewebhu lapho ungabuka khona ama-router, izinsizakalo, kanye ne-middleware. Leli phaneli aliqinisekisiwe ngokuzenzakalelayo, ngakho-ke sizobona kamuva ukuthi singalivikela kanjani ngokuqinisekiswa okuyisisekelo kusuka ekucushweni okuguquguqukayo.

Okulandelayo, amaphuzu okungena ayachazwa. Ngokuvamile, kukhona indawo yokungena web echwebeni 80 nezinye websecure ku-443. Ku web Ukuqondisa kabusha okuzenzakalelayo kuvame ukulungiselelwa ukuthi websecureukuze noma yikuphi ukufinyelela kwe-HTTP kuqondiswe ku-HTTPS:

Uhlaka olujwayelekile lungafaka isigaba http.redirections.entryPoint.to: websecure ukuphoqa lokho kuqondisa kabusha nokubeka yonke ithrafikhi ebethelwe endaweni eyodwa endaweni yokungena ephephile.

para websecure Kuboniswe ukuthi i-TLS kufanele isetshenziswe futhi kunikezwe isixhumanisi. i-certResolver (ngokwesibonelo letsencrypt) okuzoba nesibopho sokuphatha ngokuzenzakalelayo izitifiketi. Konke lokhu kusekelwa yi I-ACME, okuyinqubo esetshenziswa yi-Let's Encrypt ukukhipha nokuvuselela izitifiketi.

Kubhulokhi Abahlinzeki Umhlinzeki we-Docker ulungiselelwe, ekhomba kusokhethi unix:///var/run/docker.sockngenketho eyodwa ebalulekile: exposedByDefault: falseNgalokhu, iTraefik ayishicileli zonke iziqukathi ngokuzenzakalelayo; kuphela lezo eziphethe ilebula traefik.enable=trueUngalungisa futhi umhlinzeki wefayela (file) ukulayisha ukucushwa okwengeziwe okuguquguqukayo kusuka, isibonelo, /configurations/dynamic.yml.

Ekugcineni, ifayela elimile livame ukufaka isigaba certificatesResolverslapho kuchazwa khona isixazululo se-ACME: i-imeyili yokubhalisa, ifayela lesitoreji (ngokuvamile acme.json), uhlobo lokhiye (isibonelo EC384) kanye nendlela yokuqinisekisa (isibonelo httpChallenge endaweni yokungena webKubalulekile ukuthi setha i-imeyili yangempela Kulesi sigaba ngoba i-Let's Encrypt iyisebenzisela izaziso nokuvuselela; uma ushiya inani eliyimbumbulu noma elingakhi kahle ungase uhlangane namaphutha lapho uqala isitsha se-Traefik.

Ngaphezu kwalokhu kulungiselelwa kwe-YAML, kunezindlela zokusebenzisa ezisebenzisa Ifomethi ye-TOML (traefik.toml)Kodwa i-logic iyafana: izitifiketi zokuxazulula izigaba (isibonelo [certificatesResolvers.main.acme]), chaza izinselele (ezifana dnsChallenge con provider = "route53") bese wengeza izinketho ze-TLS ezizenzakalelayo, njenge u-forzar minVersion = "VersionTLS13" noma lungiselela uhlu lwe cipherSuites kuvunyelwe.

Ukucushwa okunamandla: i-middleware, i-TLS kanye nokuphepha

Ingxenye enamandla yeTraefik ivame ukungena kufayela elifana neli dynamic.yml, kulayishwe ngumhlinzeki wefayela. Lapha uchaza izinketho ze-middleware kanye ne-TLS okungashintshwa ngaphandle kokuqala kabusha isitsha seTraefik, okuwusizo kakhulu ekulungiseni ukuphepha ngokushesha.

Icala elijwayelekile ukudala i-header middleware, isibonelo secureHeadersenezela izinqubomgomo ezihlobene ne-HSTS kanye nokusetshenziswa okuphoqelekile kwe-HTTPS. Ku-YAML ungathola amapharamitha anjenge sslRedirect: true, forceSTSHeader: true, stsIncludeSubdomains: true, stsPreload: true futhi a stsSeconds okusezingeni eliphezulu (isibonelo, unyaka ngemizuzwana). Lokhu kuqinisa ukuphepha kwethrafikhi ohlangothini lwesiphequluli.

Enye i-middleware evamile yilena yokuqinisekisa okuyisisekelo, isibonelo user-auth zohlobo basicAuth, lapho uhlu lwabasebenzisi lumenyezelwa khona ngefomethi usuario:hashI-hash ivame ukukhiqizwa nge htpasswd futhi ifakiwe kufayela. Le middleware ivame ukuhlotshaniswa ne-router yedeshibhodi yeTraefik ukuze, ngaphezu kokufinyelela kwe-HTTPS, idinga igama lomsebenzisi nephasiwedi.

Ngaphakathi kokucushwa okufanayo okuguquguqukayo, kuvamile ukubona ibhulokhi tls.options ngephrofayili ezenzakalelayo (default) lapho kusethwe khona ama-cipher asekelwayo kanye nenguqulo encane ye-TLS, isibonelo VersionTLS12Kwezinye izinhlelo zokusebenza, izinketho eziningana ziyachazwa (isibonelo, iphrofayili ebizwa ngokuthi tls12 nezinye default) ukuze kulungiswe izinga lokuphepha ukuze lihambisane nezinsizakalo ezahlukene uma kudingeka.

Ezindaweni lapho kufiswa khona ukusetshenziswa I-TLS nayo ngaphakathi Phakathi kwezinsizakalo zeTraefik kanye nezinsizakalo ze-backend (njengePortainer), inkinga ingavela lapho lezo zinsizakalo zingenaso isitifiketi esiqashelwa yi-CA yomphakathi. Yilapho inketho iqala khona ukusebenza. insecureSkipVerify, okulungiselelwe ngaphansi providers.http.tls noma ezinkethweni ezifanele ze-TLS, ivumela i-Traefik ukuthi idlule ukuqinisekiswa kwesitifiketi sangemuva. Lokhu kuyasiza ezindaweni zelebhu noma izitifiketi zangaphakathi ezizisayinile, kodwa kufanele kusetshenziswe ngokuqapha ngoba kunciphisa ukuqinisekiswa.

Imininingwane ewusizo: ifayela dynamic.yml Ingahlelwa ngokushesha.I-Traefik ilayisha kabusha ukucushwa okunamandla ngaphandle kokudinga ukuqala kabusha, ukuze ungeze noma ususe i-middleware, ushintshe izihloko zokuphepha, noma ushintshe ukuqinisekiswa okuyisisekelo ngaphandle kokuthinta ukutholakala kwe-proxy.

ukuqamba i-docker noTraefik noPortainer ku-Docker ezimele

Esimweni se-Docker esingenalutho, ngaphandle kweSwarm, into evamile kakhulu okufanele yenziwe ukuqalisa UTraefik noPortainer nge-single docker-compose.yml okuchaza kokubili izinsizakalo kanye nenethiwekhi yohlobo lwebhuloho ehlanganyelwe ebizwa ngokuthi, isibonelo, proxy.

Isevisi Traefik Ngokuvamile isebenzisa isithombe esisemthethweni, isibonelo traefik:latest noma inguqulo ethile efana traefik:v3.4Amachweba ahlelwe ngemephu. I-80 ne-443 kwethrafikhi yewebhu, futhi kwezinye izibonelo, i-port 8080 ukuze kuvezwe iphaneli yokulawula ngaphakathi. Ngaphezu kwalokho, inketho iyengezwa restart: unless-stopped futhi ukuphepha kuqiniswa nge security_opt: - no-new-privileges:true ukunciphisa ingozi yokwanda kwamalungelo ngaphakathi kwesitsha.

Ngokuphathelene namavolumu, iTraefik idinga ukufaka isokhethi le-Docker lokufunda kuphela (/var/run/docker.sock:/var/run/docker.sock:ro) ukuthola iziqukathi, ifayela elingaguquki traefik.yml kanye nohlu lwemibhalo lapho ukucushwa okuguquguqukayo kuzogcinwa khona (./traefik-data/configurations:/configurationsIfayela lifakiwe futhi. acme.jsonYilapho iTraefik igcina khona izitifiketi ezikhishwe yi-Let's Encrypt. Leli fayela lenziwe ku-host futhi linikezwe izimvume. 600 ukuze kube ngumsebenzisi ofanele kuphela ongayifunda futhi ayibhale; uma uyishiya no-644, iTraefik ivame ukukhononda.

Isihluthulelo sokwenza uTraefik asebenze ngomlingo wakhe yilokhu amalebula esevisiPhakathi kwezinye izinto, uzothola: traefik.enable=true (ukuze umhlinzeki we-Docker adalule le nsizakalo), traefik.docker.network=proxy (ikhombisa ukuthi iyiphi inethiwekhi iTraefik okufanele iyisebenzise ukuxhumana nesitsha), kanye ne-router efana traefik.http.routers.traefik-secure, ngamalebula achaza indawo yokungena (websecure), umthetho womsingathi (isibonelo Host(`traefik.tudominio.com`)), isevisi ehambisanayo (api@internal) kanye ne-middleware yokuqinisekisa (user-auth@file).

Isevisi ye Umthwali ngokufanayo docker-compose.yml ngokuvamile isebenzisa portainer/portainer-ce:latest (noma uhlelo lwe-Enterprise uma unelayisensi). Amavolumu afanayo ayafakwa: isokhethi le-Docker, ifolda yedatha (./portainer-data:/data) futhi ngokuvamile futhi /etc/localtime ukuze izuze indawo yesikhathi yomsingathi.

Amalebula kaPortainer ayibhalisa neTraefik: traefik.enable=true, traefik.docker.network=proxyi-router yohlobo traefik.http.routers.portainer-secure nendawo yokungena websecure kanye nomthetho womsingathi ofana Host(`portainer.tudominio.com`)Ngaphezu kwalokho, isevisi okufanele isetshenziswe yiTraefik ichazwe, ikhomba echwebeni langaphakathi lePortainer, isibonelo nge traefik.http.services.portainer.loadbalancer.server.port=9000.

Njengoba konke lokhu kuqhubeka, ngemuva kokwethulwa docker compose up -d Kufolda ye-stack, iTraefik ilanda izithombe bese idala inethiwekhi. proxy Uma kumenyezelwa njengokungaphandle futhi kudalula womabili amaphaneli kuma-subdomain amisiwe, nge I-HTTPS ezenzakalelayo ngenxa ye-Let's EncryptKusukela ngaleso sikhathi kuqhubeke, ukwengeza izinsizakalo ezintsha kuyindaba yokwenza iphrojekthi yakho ibe yi-clone, ukwengeza amalebula ambalwa e-Traefik, bese uyixhuma kunethiwekhi. proxy.

Isimo se-Docker Swarm: uPortainer noTraefik eqenjini

Uma usebenzisa i-Docker Swarm, izinto ziyashintsha kancane, ngoba izinsizakalo zisetshenziswa njengezitaki futhi amanethiwekhi ngokuvamile asekelwe ekunqwabelaneni. Kodwa-ke, i-logic eyisisekelo nge-Traefik ne-Portainer ifana kakhulu: I-Traefik iyaqhubeka nokusebenza njenge-reverse proxy kanye ne-dynamic service discoverer, kanti i-Portainer ingasebenza kokubili kwimodi yokuzimela kanye nemodi ye-Portainer + agent ukuphatha ama-node akude ngaphakathi kweqembu.

Ekusetshenzisweni okuvamile kwe-Swarm, i-stack iyadalwa ngaphambi kokuba i-stack isetshenziswe. amanethiwekhi amabili okumboza iTraefik ezoyisebenzisa ukuhambisa ithrafikhi phakathi kwama-node. Ngaphezu kwalokho, kudalwa ivolumu ukuze kugcinwe idatha yePortainer (isibonelo) portainer_data) futhi, uma uyidinga, eyodwa acme.json noma isiqondisi lapho iTraefik igcina khona izitifiketi kanye nokucushwa.

El docker-compose.yml (okube sekuqala ngo docker stack deploy ukusebenzisa, isibonelo, -c portainer.yml) ngokuvamile ichaza izinsizakalo ezimbili: I-ejenti yokuthwala impahla, esebenza kumodi global kuzo zonke izinkinobho ze-Linux, kanye nensizakalo eyinhloko ye-Portainer (CE noma EE), evame ukuhlala kwimodi ephindaphindwayo enomkhawulo wokusebenza kubaphathi kuphela.

I-ejenti ye-Portainer ifaka isokhethi ye-Docker kanye nohlu lwemibhalo (/var/lib/docker/volumes) ukuze ikwazi ukuhlola izinsiza. Ixhuma kunethiwekhi yokumboza ezokwabelana ngayo neTraefik, isibonelo traefik_publicIsevisi eyinhloko ye-Portainer ingalungiselelwa ukuxhumana ne-ejenti nge-TCP (tcp://tasks.agent:9001) futhi, eqinisweni, kwezinye izibonelo lowo myalo uboniswa nge --tlsskipverify ubeke amazwana, ukuze weqe ukuqinisekiswa kwe-TLS uma kudingeka.

Ku-stack efanayo noma kwenye, iTraefik iqala ngomhlinzeki we-Docker kumodi ye-Swarm (swarmMode = true ku-TOML noma inketho efanayo kumafulegi), ebheka izinsizakalo ezimakiwe. Ukucushwa kwayo kufaka phakathi certificatesResolvers.main.acme kwe-Let's Encrypt, a dnsChallenge nomhlinzeki ofana Umzila53 Uma ufuna ukuqinisekisa izitifiketi nge-DNS, kanye nebhulokhi ye tls.options lapho, isibonelo, kuphoqelekile minVersion = "VersionTLS13" kwephrofayili ezenzakalelayo kanye nohlu olucacile luchazwa cipherSuites yephrofayili ye-TLS 1.2.

Amalebula kaPortainer eSwarm alandela ifilosofi efanayo: traefik.enable=truei-router efana traefik.http.routers.portainer con Host(`portainer.midominio.com`), traefik.http.routers.portainer.entrypoints=https (o websecure (ngokusho kwegama), kanye traefik.http.routers.portainer.tls=true ukuze unike amandla i-TLS kuleyo router. Ngaphezu kwalokho, ungacacisa i- i-certresolver con traefik.http.routers.portainer.tls.certresolver=main kanye ne-backend schema uma isevisi ikhuluma nge-HTTPS ngaphakathi traefik.http.services.portainer.loadbalancer.server.scheme=https.

Kumalogi okulungisa iphutha eTraefik eSwarm uzobona ukucushwa okukhiqizwe: ama-router afana api y portainer, izinsizakalo ezitholiwe (isibonelo portainer en http://10.0.1.12:9000 nenkonzo traefik (ekhomba i-port 8080 yedeshibhodi), futhi, uma kunenkinga ngamalebula angachazwanga kahle, imiyalezo efana "Ayikwazanga ukuchaza igama lesevisi ye-router: izinsizakalo eziningi kakhulu"okuvame ukukhombisa ukuthi kukhona ukungqubuzana noma ukuphindaphindwa kwezinsizakalo ezihlobene ne-router.

Isibonelo esincane: i-whoami, imizila kanye ne-TLS nge-Traefik

Ngaphambi kokufaka iPortainer kulesi sibalo, kuyasebenza impela ukuzama iTraefik nge-backend elula kakhulu, njengesithombe. traefik/whoamiokubuyisa ulwazi mayelana nesicelo. Lokhu kukusiza ukuqinisekisa ukuthi i-Traefik ilungiselelwe kahle nokuthi imithetho yokuqondisa iyasebenza.

Un docker-compose.yml okuyisisekelo kungafaka phakathi isevisi traefik ngesithombe traefik:v3.4, ukufaka isokhethi le-Docker nokuchaza amafulegi e-boot njenge --providers.docker=true, --providers.docker.exposedbydefault=false, --providers.docker.network=proxy kanye nendawo yokungena --entryPoints.web.address=:80Amachweba angu-80 no-8080 akhangiswa ku-host, bese kudalwa inethiwekhi. proxy okuzosebenzisa nesitsha whoami.

Isevisi whoami Iqala kunethiwekhi efanayo futhi imakwe ngokuthi traefik.enable=trueBese kuchazwa i-router ngelebula traefik.http.routers.whoami.rule=Host(`whoami.docker.localhost`) futhi kukhonjisiwe ukuthi indawo yakho yokungena webUma wenza isicelo no curl -H "Host: whoami.docker.localhost" http://localhost/Uzobona impendulo enegama lomphathi, ama-IP, ama-header nokunye, okuqinisekisa ukuthi i-Traefik ihambisa ngendlela efanele.

Kusukela lapho, kulula. engeza umzila ngezindlelaIsibonelo, ungakha enye isevisi. whoami-api ngesithombe esifanayo, kunethiwekhi efanayo, bese usimaka ngomthetho wohlobo Host(`whoami.docker.localhost`) && PathPrefix(`/api`)Ngakho-ke, impande / Iya ku whoami yokuqala kanye nezicelo zokuthi /api ngizobakhonza whoami-apiUngakuqinisekisa lokhu ngokwenza izicelo zokuthi / kakade /api nomphathi ofanayo.

Ukwenza kusebenze TLS Kulesi simo sendawo, enye inketho ukukhiqiza isitifiketi esizisayinele sona sesizinda *.docker.localhost con opensslUdala isiqondisi certs, ukhiqiza local.key y local.crt, bese ufaka ifayela elinamandla (isibonelo dynamic/tls.yml) nesigaba tls: kanye nemizila certFile y keyFile ekhomba lawo mafayela.

Okulandelayo, ubuyekeza incazelo yesevisi yeTraefik ku docker-compose.yml ukufaka ifolda ./certs nefolda ./dynamic ngaphakathi kwesitsha, usebenzisa i-API evikelekile nge --api.dashboard=true, udala indawo yokungena websecure (--entryPoints.websecure.address=:443) bese unika amandla i-TLS lapho nge --entryPoints.websecure.http.tls=trueUphinde ulebule i-router yedeshibhodi kanye nama-router e- whoami ukuze basebenzise websecure futhi ube tls=true.

Uma sekuvuliwe, uzokwazi ukufinyelela https://whoami.docker.localhost/ kanye nephaneli yeTraefik enesitifiketi esizisayinele yona, samukela isexwayiso sokuphepha sesiphequluli. Lokhu okuhlangenwe nakho kufana kakhulu nalokho ozoba nakho kamuva ekukhiqizweni nge-Let's Encrypt, kodwa ngaphandle kokuthembela kumaseva e-DNS omphakathi.

Imikhuba emihle kakhulu, ukuthunyelwa kohlelo lokusebenza, kanye nokuxazulula izinkinga ezivamile

Iphethini elilodwa eliphindaphindwayo kuzo zonke lezi zibonelo ukuthi I-Traefik yenza kube lula kakhulu ukuthunyelwa kwezinhlelo zokusebenza ezintshaUma usunayo i-base stack yakho (i-Traefik + i-Portainer + inethiwekhi) proxy (+ izitifiketi), ukwengeza isevisi entsha kuvame ukwehla kube:

Yenza iphrojekthi ibe yi-Clone noma ukopishe eyakho docker-compose.yml kuseva, khomba isizinda esincane ekhelini le-IP lomsingathi usebenzisa i- irekhodi A ku-DNS yakho (isibonelo app.tudominio.com), bese ufaka amalebula ayisihluthulelo kusevisi: traefik.enable=true, traefik.docker.network=proxy kanye ne-router enomthetho we-host waleso sizinda esincane, echaza indawo yokungena evikelekile websecure futhi i isevisi enembobo yangaphakathi efanele.

Izifundo eziningi zingabonisa, isibonelo, ukuqaliswa kohlelo lokusebenza oluncane FastAPI Kuhlukanisiwe: kunezelwa amalebula amane, okuqinisekisa ukuthi ijoyina inethiwekhi proxy esigabeni networks i-del docker-compose.ymlfuthi ngemva kokwenza docker compose up -d Uhlelo lokusebenza luvela ngokuzenzakalelayo kudeshibhodi yeTraefik ene-TLS evuliwe. Ukutholakala kweTraefik ngokuzenzakalelayo kusho ukuthi awudingi ngisho nokulungisa izilungiselelo zayo ezimile.

Ukuze uqinisekise ukuthi konke kuhamba kahle, kubalulekile ukunaka imininingwane embalwa: ungasebenzisi kabusha isihlonzi se-router esifanayo Kuzinhlelo zokusebenza ezahlukahlukene, hlola ukuthi kukhona isevisi eyodwa kuphela ehlotshaniswa ne-router ngayinye (ukugwema iphutha "lezinsizakalo eziningi kakhulu"), sebenzisa amagama enethiwekhi ahambisanayo (isibonelo, proxy kuzo zonke izitaki ofuna ukuziveza), futhi, uma usebenzisa i-Let's Encrypt, qiniseka ukuthi acme.json Inezimvume ezingu-600 futhi i-imeyili elungiselelwe iyasebenza.

Ezindaweni zeSwarm, hlola futhi ukuthi ukucushwa kweTraefik kufaka phakathi umhlinzeki weDocker. swarmMode=true y watch=truenokuthi imikhawulo yezinsizakalo (isibonelo node.role == manager (nge-Portainer) ayingqubuzani nokuthi i-Traefik isetshenziswa kuphi. Amalogi okulungisa iphutha ayinkimbinkimbi kakhulu kodwa ayisihluthulelo sokuthola izinkinga zomzila noma ze-TLS.

I-Docker ehlanganisiwe , i-Traefik, ne-Portainer, ungasetha indawo ephelele yokuhlelwa okulula kuseva eyodwa, ngamadeshibhodi ezithombe, izitifiketi ezizenzakalelayo, kanye nokugeleza kokuthunyelwa okusheshayo kakhulu, lapho ukwengeza, ukubuyekeza, noma ukususa izinsizakalo kuncishiswa ekulungiseni imigqa embalwa ye-YAML nokuvumela i-Traefik ukuthi yenze umsebenzi ongcolile wokubuyisela emuva iphrojekthi kanye ne-TLS.