{"id":76494,"date":"2020-04-02T13:42:51","date_gmt":"2020-04-02T11:42:51","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine"},"modified":"2020-04-02T13:42:51","modified_gmt":"2020-04-02T11:42:51","slug":"docker-i-vmware-workstation-na-odnoj-windows-mashine","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","title":{"rendered":"Docker dhe VMWare Workstation n\u00eb nj\u00eb makin\u00eb Windows","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Detyra ishte e thjesht\u00eb, t\u00eb vendos\u00ebsh Docker n\u00eb laptopin tim t\u00eb pun\u00ebs me Windows, ku tashm\u00eb kishte nj\u00eb zhuar. Instalova Docker Desktop, krijova kontenier\u00eb, gjith\u00e7ka ishte n\u00eb rregull, por shpejt e kuptova se VMware Workstation kishte ndaluar s\u00eb funksionuari me nj\u00eb gabim:<\/p>\n

VMware Workstation dhe Device\/Credential Guard nuk jan\u00eb t\u00eb p\u00ebrshtatshme. VMware Workstation mund t\u00eb ekzekutohet pas \u00e7aktivizimit t\u00eb Device\/Credential Guard.<\/code><\/pre>\n
\n<\/a><\/noindex><\/p>\n
Puna u ndal, duhet ta rregulloj menj\u00ebher\u00eb<\/h3>\n
\n\"Docker
\n
\nP\u00ebrmes nj\u00eb k\u00ebrkimi n\u00eb Google, u zbulua se ky gabim ndodhte p\u00ebr shkak t\u00eb papajtueshm\u00ebris\u00eb s\u00eb VMware Workstation dhe Hyper-V n\u00eb t\u00eb nj\u00ebjt\u00ebn makin\u00eb. Problemi \u00ebsht\u00eb i njohur dhe ka nj\u00eb zgjidhje zyrtare nga VMware si ta rregullosh<\/a><\/noindex>, me nj\u00eb lidhje n\u00eb baz\u00ebn e njohurive t\u00eb Microsoft Menaxho Windows Defender Credential Guard<\/a><\/noindex>. Zgjidhja p\u00ebrfshin \u00e7aktivizimin e Defender Credential Guard (m\u00eb ndihmoi pika 4 e seksionit Disable Windows Defender Credential Guard):<\/p>\n
mountvol X: \/s\ncopy %WINDIR%System32SecConfig.efi X:EFIMicrosoftBootSecConfig.efi \/Y\nbcdedit \/create {0cb3b571-2f2e-4343-a879-d86a476d7215} \/d "DebugTool" \/application osloader\nbcdedit \/set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "EFIMicrosoftBootSecConfig.efi"\nbcdedit \/set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}\nbcdedit \/set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO\nbcdedit \/set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:\nmountvol X: \/d<\/code><\/pre>\n
\nPas renovimit t\u00eb Windows, do t'ju pyes\u00eb n\u00ebse d\u00ebshironi t\u00eb \u00e7aktivizoni Defender Credential Guard. Po! K\u00ebshtu, VMWare Workstation do t'i kthehet funksionimit normal, dhe ne do t\u00eb jemi n\u00eb t\u00eb nj\u00ebjtin vend si para instalimit t\u00eb Docker.<\/p>\n
Nuk kam gjetur zgjidhje si t\u00eb pajtojm\u00eb Hyper-V dhe VMWare Workstation, shpresoj q\u00eb n\u00eb versionet e reja ata do t\u00eb bashk\u00ebpunojn\u00eb. <\/p>\n
Nj\u00eb rrug\u00eb tjet\u00ebr<\/h3>\n
\nPrej koh\u00ebsh kam kaluar n\u00eb VMWare Workstation p\u00ebr q\u00ebllime t\u00eb ndryshme, p\u00ebrpiqesha t\u00eb kaloj n\u00eb Hyper-V dhe VirtualBox, por funksionaliteti nuk m\u00eb k\u00ebnaqte p\u00ebr nevojat e mia, prandaj vazhdoj t\u00eb q\u00ebndroj k\u00ebtu. Doli se ka nj\u00eb zgjidhje si t\u00eb bashk\u00ebpunojm\u00eb VMWare, Docker dhe VSCode n\u00eb nj\u00eb mjedis pune.<\/p>\n
Docker Machine<\/b><\/a><\/noindex> \u2014 lejon t\u00eb \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u043f\u0440\u043e\u0441 n\u00eb Docker Engine n\u00eb nj\u00eb host virtual dhe t\u00eb lidheni me t\u00eb si n\u00eb distanc\u00eb, ashtu edhe n\u00eb vend. Dhe p\u00ebr t\u00eb ekziston nj\u00eb driver kompatibiliteti me VMWare Workstation, linku n\u00eb GitHub<\/a><\/noindex><\/p>\n
Nuk do ta p\u00ebrs\u00ebris udh\u00ebzimin p\u00ebr instalim, vet\u00ebm list\u00ebn e p\u00ebrb\u00ebr\u00ebsve:<\/p>\n
    \n
  1. Docker Toolbox<\/a><\/noindex> (Docker Machine<\/a><\/noindex> n\u00eb paket\u00eb)<\/li>\n
  2. Docker Machine VMware Workstation Driver<\/a><\/noindex><\/li>\n
  3. Docker Desktop<\/li>\n<\/ol>\n
    \nPo, Docker Desktop, fatkeq\u00ebsisht, gjithashtu do t\u00eb nevojitet. N\u00ebse e keni fshir\u00eb, duhet ta instaloni p\u00ebrs\u00ebri, por k\u00ebt\u00eb her\u00eb duke hequr kutin\u00eb p\u00ebr ndryshimet n\u00eb OS, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb mos thyejn\u00eb p\u00ebrs\u00ebri VMWare Workstation.<\/p>\n
    Dua t\u00eb theksoj q\u00eb gjith\u00e7ka funksionon shk\u00eblqyer nga p\u00ebrdoruesi i zakonsh\u00ebm, programet e instalimit do t\u00eb k\u00ebrkojn\u00eb eskalimin e t\u00eb drejtave kur t\u00eb jet\u00eb e nevojshme, por t\u00eb gjitha komandat n\u00eb linj\u00ebn e komand\u00ebs dhe skriptet ekzekutohen nga p\u00ebrdoruesi aktual.<\/i><\/p>\n
    N\u00eb p\u00ebrfundim, me komand\u00ebn:<\/p>\n
    $ docker-machine create --driver=vmwareworkstation dev<\/code><\/pre>\n
    \nnga Boot2Docker do t\u00eb krijohet nj\u00eb virtual k\u00ebtu dev brenda s\u00eb cil\u00ebs do t\u00eb jet\u00eb Docker.<\/p>\n
    Kjo virtual k\u00ebtu mund t\u00eb lidhet n\u00eb nd\u00ebrfaqen grafike t\u00eb VMWare Workstation, duke hapur skedarin p\u00ebrkat\u00ebs vmx. Por kjo nuk \u00ebsht\u00eb e domosdoshme, pasi VSCode tani duhet t\u00eb niset me skriptin PowerShell (p\u00ebr arsye t\u00eb panjohura, docker-machine dhe docker-machine-driver-vmwareworkstation p\u00ebrfunduan pik\u00ebrisht n\u00eb dosjen bin):<\/p>\n
    cd ~\/bin\n.\/docker-machine env dev | Invoke-Expression\ncode<\/code><\/pre>\n
    \nVSCode do t\u00eb hapet p\u00ebr t\u00eb punuar me kodin n\u00eb makin\u00ebn lokale dhe Docker n\u00eb virtual k\u00ebtu. Ky plug-in Docker for Visual Studio Code<\/a><\/noindex> mund\u00ebson menaxhimin e leht\u00eb t\u00eb konteiner\u00ebve n\u00eb virtual k\u00ebtu pa hyr\u00eb n\u00eb konsol\u00eb.<\/p>\n
    Sfidat:<\/b><\/p>\n
    Gjat\u00eb procesit t\u00eb krijimit t\u00eb docker-machine, procesi ngeci: <\/p>\n
    Duke pritur q\u00eb SSH t\u00eb jet\u00eb n\u00eb dispozicion...<\/code><\/pre>\n
    \n\"Docker
    \n
    \nDhe pas nj\u00eb kohe t\u00eb caktuar p\u00ebrfundoi me tejkalimin e p\u00ebrpjekjeve p\u00ebr t\u00eb vendosur lidhjen me virtual k\u00ebtu.<\/p>\n
    E gjith\u00eb \u00e7\u00ebshtja \u00ebsht\u00eb politika p\u00ebr certifikatat. Kur krijoni nj\u00eb makin\u00eb virtuale, do t\u00eb keni nj\u00eb katalog ~.dockermachinemachinesdev, n\u00eb t\u00eb cilin do t\u00eb gjeni skedar\u00ebt e certifikat\u00ebs p\u00ebr lidhjen SSH: id_rsa, id_rsa.pub. OpenSSH mund t\u00eb refuzoj\u00eb t\u2019i p\u00ebrdor\u00eb ata, sepse mendon se ata kan\u00eb probleme me t\u00eb drejtat e aksesit. Por docker-machine nuk do t\u2019jua thot\u00eb asgj\u00eb p\u00ebr k\u00ebt\u00eb, thjesht do t\u00eb vazhdoj\u00eb t\u00eb rikthehet derisa t\u2019i m\u00ebrzit\u00eb.<\/p>\n
    Zgjidhja:<\/b> Sapo t\u00eb filloj\u00eb krijimi i nj\u00eb makine virtuale t\u00eb re, hyjm\u00eb n\u00eb katalogun ~.dockermachinemachinesdev dhe ndryshojm\u00eb t\u00eb drejtat p\u00ebr skedar\u00ebt e p\u00ebrmendur, nj\u00eb nga nj\u00eb.<\/p>\n
    Pronari i skedarit duhet t\u00eb jet\u00eb p\u00ebrdoruesi aktual, t\u00eb drejt\u00eb t\u00eb plota ka vet\u00ebm p\u00ebrdoruesi aktual dhe SYSTEM, nd\u00ebrsa t\u00eb gjith\u00eb p\u00ebrdoruesit e tjer\u00eb, duke p\u00ebrfshir\u00eb grupin e administrator\u00ebve dhe vet\u00eb administrator\u00ebt duhet t\u00eb fshihen.<\/p>\n
    Gjithashtu mund t\u00eb ket\u00eb probleme me konvertimin e rrug\u00ebve absolute nga formati Windows n\u00eb Posix, dhe me lidhjen e volumen\u00ebve q\u00eb p\u00ebrmbajn\u00eb lidhje simbolike. Por kjo \u00ebsht\u00eb nj\u00eb histori tjet\u00ebr.
    \n
    Burimi:     habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
    \u0417\u0430\u0434\u0430\u0447\u0430 \u0431\u044b\u043b\u043e \u043f\u0440\u043e\u0441\u0442\u043e\u0439, \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c Docker \u043d\u0430 \u0441\u0432\u043e\u0439 \u0440\u0430\u0431\u043e\u0447\u0438\u0439 \u043d\u043e\u0443\u0442\u0431\u0443\u043a \u0441 Windows, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0443\u0436\u0435 \u0438 \u0442\u0430\u043a \u0437\u043e\u043e\u043f\u0430\u0440\u043a. \u041f\u043e\u0441\u0442\u0430\u0432\u0438\u043b Docker Desktop \u0441\u043e\u0437\u0434\u0430\u043b \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b, \u0432\u0441\u0451 \u043e\u043a, \u0432\u043e\u0442 \u0442\u043e\u043b\u044c\u043a\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b, \u0447\u0442\u043e VMWare Workstation \u043f\u0435\u0440\u0435\u0441\u0442\u0430\u043b\u0430 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u043a\u0438 \u0441 \u043e\u0448\u0438\u0431\u043a\u043e\u0439: VMware Workstation and Device\/Credential Guard are not compatible. VMware Workstation can be run after disabling Device\/Credential Guard. \u0420\u0430\u0431\u043e\u0442\u0430 \u0432\u0441\u0442\u0430\u043b\u0430, […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":76495,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-76494","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Docker dhe VMWare Workstation n\u00eb t\u00eb nj\u00ebjt\u00ebn makin\u00eb Windows | ProHoster","description":"Det\u00ebza ishte e thjesht\u00eb, t\u00eb vendosje Docker n\u00eb laptopin t\u00ebnd t\u00eb pun\u00ebs me Windows, n\u00eb t\u00eb cilin tashm\u00eb kishte nj\u00eb kopsht zoologjik. Vendosa Docker Desktop, krijova kontejner\u00eb, gjith\u00e7ka ishte n\u00eb rregull, por shpejt e kuptova se VMWare Workstation nuk fillonte t\u00eb virtualizonte me gabimin: VMware Workstation dhe Device\/Credential Guard nuk jan\u00eb t\u00eb p\u00ebrputhshme. VMware Workstation mund t\u00eb ekzekutohet pas \u00e7aktivizimit t\u00eb Device\/Credential Guard. Puna u pengua,","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47Docker \u0438 VMWare Workstation \u043d\u0430 \u043e\u0434\u043d\u043e\u0439 Windows \u043c\u0430\u0448\u0438\u043d\u0435 | ProHoster","og:description":"\u0417\u0430\u0434\u0430\u0447\u0430 \u0431\u044b\u043b\u043e \u043f\u0440\u043e\u0441\u0442\u043e\u0439, \u043f\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c Docker \u043d\u0430 \u0441\u0432\u043e\u0439 \u0440\u0430\u0431\u043e\u0447\u0438\u0439 \u043d\u043e\u0443\u0442\u0431\u0443\u043a \u0441 Windows, \u043d\u0430 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u0443\u0436\u0435 \u0438 \u0442\u0430\u043a \u0437\u043e\u043e\u043f\u0430\u0440\u043a. \u041f\u043e\u0441\u0442\u0430\u0432\u0438\u043b Docker Desktop \u0441\u043e\u0437\u0434\u0430\u043b \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u044b, \u0432\u0441\u0451 \u043e\u043a, \u0432\u043e\u0442 \u0442\u043e\u043b\u044c\u043a\u043e \u0431\u044b\u0441\u0442\u0440\u043e \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0438\u043b, \u0447\u0442\u043e VMWare Workstation \u043f\u0435\u0440\u0435\u0441\u0442\u0430\u043b\u0430 \u0437\u0430\u043f\u0443\u0441\u043a\u0430\u0442\u044c \u0432\u0438\u0440\u0442\u0443\u0430\u043b\u043a\u0438 \u0441 \u043e\u0448\u0438\u0431\u043a\u043e\u0439: VMware Workstation and Device\/Credential Guard are not compatible. VMware Workstation can be run after disabling Device\/Credential Guard. \u0420\u0430\u0431\u043e\u0442\u0430 \u0432\u0441\u0442\u0430\u043b\u0430,","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-04-02T11:42:51+00:00","article:modified_time":"2020-04-02T11:42:51+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"76494","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:35:42","updated":"2022-09-28 07:26:54"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/76494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=76494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/76494\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/76495"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=76494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=76494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=76494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}