I-ProHoster > Π‘Π»ΠΎΠ³ > Ukuphatha > I-Docker ne-VMWare Workstation emshinini ofanayo we-Windows

I-Docker ne-VMWare Workstation emshinini ofanayo we-Windows

Umsebenzi wawulula, faka i-Docker kukhompyutha yami ephathekayo ye-Windows, esivele ine-zoo. Ngifake i-Docker Desktop futhi ngenza iziqukathi, konke kulungile, kodwa ngathola ngokushesha ukuthi i-VMWare Workstation iyeke ukusebenzisa imishini ebonakalayo ngephutha:

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard.

Umsebenzi umile, kuyaphuthuma ukulungisa

I-Docker ne-VMWare Workstation emshinini ofanayo we-Windows

Ngokungena ku-googling, kwatholakala ukuthi leli phutha lenzeka ngenxa yokungahambelani kwe-VMWare Workstation ne-Hyper-V emshinini ofanayo. Inkinga iyaziwa futhi kunesixazululo esisemthethweni se-VMWare esifana nalesi lungisa, enesixhumanisi se-Microsoft Knowledge Base Phatha I-Windows Defender Credential Guard. Isixazululo ukukhubaza I-Defender Credential Guard (into 4 yesigaba Se-Windows Defender Credential Guard yangisiza):

mountvol X: /s
copy %WINDIR%System32SecConfig.efi X:EFIMicrosoftBootSecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "EFIMicrosoftBootSecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Ngemuva kokuqala kabusha, iWindows izobuza ukuthi ufuna ngempela ukukhubaza i-Defender Credential Guard. Yebo! Ngale ndlela, i-VMWare Workstation izobuyela ekusebenzeni okujwayelekile, futhi sizozithola sisendaweni efanayo nangaphambi kokufaka idokha.

Angikasitholi isisombululo sendlela yokuvumelanisa i-Hyper-V ne-VMWare Workstation, ngithemba ukuthi bazoba abangani ezinguqulweni ezintsha.

Enye indlela

Sekuyisikhathi eside ngiwumlutha we-VMWare Workstation ngezinjongo ezihlukahlukene, ngazama ukwehla ku-Hyper-V ne-VirtualBox, kodwa ukusebenza akuzange kunelise imisebenzi yami, ngakho-ke ngihlala kuze kube yilolu suku. Kwavela ukuthi kukhona isixazululo indlela yokwenza abangane VMWare, Docker futhi VSCode endaweni eyodwa yokusebenza.

Umshini We-Docker - ikuvumela ukuthi usebenzise Injini ye-Docker kumsingathi obonakalayo futhi uxhume kuyo ukude nasendaweni. Futhi kukhona umshayeli we-VMWare Workstation wokuhambisana kwayo, isixhumanisi ku-github

Ngeke ngiphinde ngixoxele imiyalelo yokufaka ikakhulukazi, uhlu lwezithako kuphela:

  1. I-Docker Toolbox (Umshini We-Docker kuhlanganisiwe)
  2. I-Docker Machine VMware Workstation Driver
  3. Ideskithophu yeDocker

Yebo, i-Docker Desktop, ngeshwa, nayo izodingeka. Uma uyibhidlizile, bese uyifake futhi, kodwa kulokhu ususa ibhokisi lokuhlola mayelana nokwenza izinguquko ku-OS, ukuze ungaphuli i-VMWare Workstation futhi.

Ngifuna ukuqaphela ngaso leso sikhathi ukuthi yonke into isebenza kahle kumsebenzisi olula, izinhlelo zokufaka zizocela ukwanda kwamalungelo lapho zidinga, kodwa yonke imiyalo emgqeni womyalo kanye nemibhalo ikhishwa kumsebenzisi wamanje.

Ngenxa yalokho, iqembu:

$ docker-machine create --driver=vmwareworkstation dev

kusuka ku-Boot2Docker, kuzokwakhiwa i-dev virtualka ngaphakathi okuzoba yi-Docker.

Lo mshini we-virtual ungaxhunywa ku-VMWare Workstation GUI ngokuvula ifayela le-vmx elihambisanayo. Kepha lokhu akudingekile, ngoba i-VSCode manje izodinga ukusebenzisa iskripthi se-PowerShell (ngesizathu esithile, umshini wami we-docker kanye ne-docker-machine-driver-vmwareworkstation kugcine kufolda yomgqomo):

cd ~/bin
./docker-machine env dev | Invoke-Expression
code

I-VSCode izovula ukusebenza ngekhodi emshinini wendawo kanye ne-docker emshinini we-virtual. Xhuma I-Docker yekhodi ye-Visual Studio ikuvumela ukuthi uphathe iziqukathi kalula emshinini obonakalayo ngaphandle kokungena kukhonsoli.

Ubunzima:

Ngenqubo yokudala umshini we-docker, inqubo yangilenga: 

Waiting for SSH to be available...

I-Docker ne-VMWare Workstation emshinini ofanayo we-Windows

Futhi ngemva kwesikhashana kuphelile ngemizamo eyengeziwe yokusungula uxhumano nomshini obonakalayo.

Konke kumayelana nenqubomgomo yesitifiketi. Lapho udala umshini we-virtual, uzoba nenkomba ethi ~.dockermachinemachinesdev kulolu hlu lwemibhalo kuzoba namafayela esitifiketi okuxhunywa ngawo nge-SSH: id_rsa, id_rsa.pub. I-OpenSSH ingase yenqabe ukuzisebenzisa ngoba icabanga ukuthi zinezinkinga zemvume. Umshini we-docker kuphela ongeke ukutshele lutho ngalokhu, kodwa uzomane uxhumeke kuze kube yilapho usunesithukuthezi.

Isixazululo: Lapho nje ukwakhiwa komshini omusha we-virtual kuqala, siya ku- ~ .dockermachinemachinesdev lwemibhalo futhi sishintshe amalungelo kumafayela ashiwo, elilodwa ngesikhathi.

Ifayela kufanele libe ngelomsebenzisi wamanje, umsebenzisi wamanje kuphela kanye ne-SYSTEM abanokufinyelela okugcwele, bonke abanye abasebenzisi, kuhlanganise neqembu labalawuli kanye nabalawuli ngokwabo, kufanele basuswe.

Kungase futhi kube nezinkinga ekuguquleni izindlela eziphelele zisuka ku-Windows ziye kufomethi ye-Posix, namavolumu abophezelayo aqukethe izixhumanisi ezingokomfanekiso. Kodwa leyo ngenye indaba.

Source: www.habr.com

Engeza amazwana