{"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\/ro\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","title":{"rendered":"Docker \u0219i VMWare Workstation pe aceea\u0219i ma\u0219in\u0103 Windows","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Sarcina a fost simpl\u0103, s\u0103 instalez Docker pe laptopul meu de lucru cu Windows, pe care deja aveam un haos. Am instalat Docker Desktop, am creat containere, totul bine, dar am descoperit rapid c\u0103 VMWare Workstation a \u00eencetat s\u0103 mai porneasc\u0103 ma\u0219inile virtuale cu o eroare:<\/p>\n

VMware Workstation \u0219i Device\/Credential Guard nu sunt compatibile. VMware Workstation poate fi rulat dup\u0103 dezactivarea Device\/Credential Guard.<\/code><\/pre>\n
\n<\/a><\/noindex><\/p>\n
Lucrurile s-au oprit, trebuie s\u0103 repar urgent.<\/h3>\n
\n\"Docker
\n
\nPrin c\u0103utare pe Google, am aflat c\u0103 aceast\u0103 eroare apare din cauza incompatibilit\u0103\u021bii dintre VMWare Workstation \u0219i Hyper-V pe aceea\u0219i ma\u0219in\u0103. Problema este cunoscut\u0103 \u0219i exist\u0103 o solu\u021bie oficial\u0103 de la VMWare pe cum s\u0103 o repari<\/a><\/noindex>, cu un link c\u0103tre baza de cuno\u0219tin\u021be Microsoft Gestioneaz\u0103 Windows Defender Credential Guard<\/a><\/noindex>. Solu\u021bia const\u0103 \u00een dezactivarea Defender Credential Guard (m-a ajutat punctul 4 din sec\u021biunea Dezactivateaz\u0103 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
\nDup\u0103 repornirea Windows, va \u00eentreba dac\u0103 vreau cu adev\u0103rat s\u0103 dezactivez Defender Credential Guard. Da! Astfel, VMWare Workstation va reveni la func\u021bionarea normal\u0103, iar noi ne vom g\u0103si \u00een aceea\u0219i situa\u021bie ca \u00eenainte de a instala Docker.<\/p>\n
Solu\u021biile pentru a \u00eemp\u0103ca Hyper-V \u0219i VMWare Workstation nu le-am g\u0103sit, sper c\u0103 \u00een versiunile viitoare se vor \u00een\u021belege. <\/p>\n
Un alt mod<\/h3>\n
\nDe mult timp folosesc VMWare Workstation pentru diverse scopuri, am \u00eencercat s\u0103 trec pe Hyper-V \u0219i VirtualBox, dar func\u021bionalitatea nu a satisf\u0103cut cerin\u021bele mele, a\u0219a c\u0103 \u00eenc\u0103 utilizez VMWare. Se pare c\u0103 exist\u0103 o solu\u021bie pentru a alinia VMWare, Docker \u0219i VSCode \u00eentr-un singur mediu de lucru.<\/p>\n
Docker Machine<\/b><\/a><\/noindex> \u2014 permite rularea Docker Engine pe un gazd\u0103 virtual\u0103 \u0219i conectarea la acesta at\u00e2t de la distan\u021b\u0103, c\u00e2t \u0219i local. \u0218i pentru aceasta exist\u0103 un driver de compatibilitate cu VMWare Workstation, link c\u0103tre GitHub<\/a><\/noindex><\/p>\n
Nu voi relua \u00een detaliu instruc\u021biunile de instalare, doar lista ingredientelor:<\/p>\n
    \n
  1. Docker Toolbox<\/a><\/noindex> (Docker Machine<\/a><\/noindex> inclus\u0103)<\/li>\n
  2. Docker Machine VMware Workstation Driver<\/a><\/noindex><\/li>\n
  3. Docker Desktop<\/li>\n<\/ol>\n
    \nDa, Docker Desktop, din p\u0103cate, va fi necesar. Dac\u0103 l-a\u021bi dezinstalat, atunci reinstala\u021bi-l, dar de data aceasta f\u0103r\u0103 a bifa c\u0103su\u021ba pentru modific\u0103ri \u00een sistemul de operare, pentru a nu strica din nou VMWare Workstation.<\/p>\n
    Vreau s\u0103 subliniez c\u0103 totul func\u021bioneaz\u0103 perfect de la un utilizator obi\u0219nuit, programele de instalare vor cere escaladarea privilegiilor c\u00e2nd va fi necesar, dar toate comenzile \u00een linia de comand\u0103 \u0219i scripturile sunt executate de utilizatorul curent.<\/i><\/p>\n
    \u00cen concluzie, comanda:<\/p>\n
    $ docker-machine create --driver=vmwareworkstation dev<\/code><\/pre>\n
    \nO virtual machine dev va fi creat\u0103 din Boot2Docker, \u00een interiorul c\u0103reia va fi Docker.<\/p>\n
    Aceast\u0103 ma\u0219in\u0103 virtual\u0103 poate fi conectat\u0103 la interfa\u021ba grafic\u0103 VMWare Workstation, deschiz\u00e2nd fi\u0219ierul vmx corespunz\u0103tor. \u00cens\u0103 aceasta nu este obligatorie, deoarece acum va trebui s\u0103 lans\u0103m scriptul PowerShell \u00een VSCode (dintr-un motiv oarecare, docker-machine \u0219i docker-machine-driver-vmwareworkstation s-au aflat \u00een folderul bin):<\/p>\n
    cd ~\/bin\n.\/docker-machine env dev | Invoke-Expression\ncode<\/code><\/pre>\n
    \nSe va deschide VSCode pentru a lucra cu codul pe ma\u0219ina local\u0103 \u0219i Docker \u00een ma\u0219ina virtual\u0103. Pluginul Docker pentru Visual Studio Code<\/a><\/noindex> permite gestionarea convenabil\u0103 a containerelor din ma\u0219ina virtual\u0103 f\u0103r\u0103 a accesa consola.<\/p>\n
    Dificult\u0103\u021bi:<\/b><\/p>\n
    \u00cen timpul cre\u0103rii docker-machine, procesul meu s-a blocat: <\/p>\n
    Waiting for SSH to be available...<\/code><\/pre>\n
    \n\"Docker
    \n
    \n\u0218i dup\u0103 un timp s-a \u00eencheiat cu dep\u0103\u0219irea \u00eencerc\u0103rilor de a stabili conexiunea cu ma\u0219ina virtual\u0103.<\/p>\n
    Totul se datoreaz\u0103 politicii privind certificatele. La crearea ma\u0219inii virtuale, va ap\u0103rea un folder ~.dockermachinemachinesdev \u00een care vor fi fi\u0219ierele certificatului pentru conexiunea SSH: id_rsa, id_rsa.pub. OpenSSH poate refuza s\u0103 le foloseasc\u0103, consider\u00e2nd c\u0103 au probleme cu permisiunile. Dar docker-machine nu v\u0103 va spune nimic despre asta, pur \u0219i simplu va \u00eencerca s\u0103 se reconecteze p\u00e2n\u0103 c\u00e2nd se va s\u0103tura.<\/p>\n
    Solu\u021bia:<\/b> Odat\u0103 ce \u00eencepe crearea noii ma\u0219ini virtuale, intr\u0103m \u00een folderul ~.dockermachinemachinesdev \u0219i schimb\u0103m permisiunile pe fi\u0219ierele respective, pe r\u00e2nd.<\/p>\n
    Proprietarul fi\u0219ierului trebuie s\u0103 fie utilizatorul curent, iar accesul total s\u0103 fie doar pentru utilizatorul curent \u0219i SYSTEM, ceilal\u021bi utilizatori, inclusiv grupul de administratori \u0219i administratorii \u00een\u0219i\u0219i, trebuind elimina\u021bi.<\/p>\n
    De asemenea, pot exista probleme cu transformarea c\u0103ilor absolute din format Windows \u00een format Posix \u0219i cu legarea volumelor care con\u021bin link-uri simbolice. Dar aceasta este o alt\u0103 poveste.
    \n
    Sursa:     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 \u0219i VMWare Workstation pe aceea\u0219i ma\u0219in\u0103 Windows | ProHoster","description":"Sarcina a fost simpl\u0103, s\u0103 instalez Docker pe laptopul meu de lucru cu Windows, pe care deja avea un adev\u0103rat zoo.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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.","og:url":"https:\/\/prohoster.info\/ro\/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","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/76494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=76494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/76494\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/76495"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=76494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=76494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=76494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}