{"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\/pl\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","title":{"rendered":"Docker i VMWare Workstation na jednym komputerze z systemem Windows","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Zadanie by\u0142o proste, zainstalowa\u0107 Docker na swoim laptopie z Windows, na kt\u00f3rym i tak ju\u017c panowa\u0142a ba\u0142agan. Zainstalowa\u0142em Docker Desktop, stworzy\u0142em kontenery, wszystko w porz\u0105dku, tylko szybko odkry\u0142em, \u017ce VMWare Workstation przesta\u0142o uruchamia\u0107 wirtualne maszyny z b\u0142\u0119dem:<\/p>\n

VMware Workstation i Device\/Credential Guard s\u0105 ze sob\u0105 niekompatybilne. VMware Workstation mo\u017cna uruchomi\u0107 po wy\u0142\u0105czeniu Device\/Credential Guard.<\/code><\/pre>\n
\n<\/a><\/noindex><\/p>\n
Praca stan\u0119\u0142a, musz\u0119 szybko naprawi\u0107<\/h3>\n
\n\"Docker
\n
\nMetod\u0105 googlenia uda\u0142o si\u0119 ustali\u0107, \u017ce ten b\u0142\u0105d wynika z niezgodno\u015bci VMWare Workstation i Hyper-V na jednym komputerze. Problem jest znany, a VMware ma oficjalne rozwi\u0105zanie, jak to naprawi\u0107<\/a><\/noindex>, z odniesieniem do bazy wiedzy Microsoftu Zarz\u0105dzaj Windows Defender Credential Guard<\/a><\/noindex>. Rozwi\u0105zanie sprowadza si\u0119 do wy\u0142\u0105czenia Defender Credential Guard (pom\u00f3g\u0142 mi punkt 4 sekcji Wy\u0142\u0105cz 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
\nPo ponownym uruchomieniu Windows zapyta, czy naprawd\u0119 chcesz wy\u0142\u0105czy\u0107 Defender Credential Guard. Tak! Dzi\u0119ki temu VMWare Workstation wr\u00f3ci do normalnej pracy, a my znajdziemy si\u0119 w tym samym miejscu, co przed instalacj\u0105 Dockera.<\/p>\n
Nie znalaz\u0142em rozwi\u0105zania, jak pogodzi\u0107 Hyper-V i VMWare Workstation, mam nadziej\u0119, \u017ce w nowych wersjach b\u0119d\u0105 wsp\u00f3\u0142pracowa\u0107. <\/p>\n
Inna droga<\/h3>\n
\nJu\u017c od dawna korzystam z VMWare Workstation do r\u00f3\u017cnych cel\u00f3w, pr\u00f3bowa\u0142em przej\u015b\u0107 na Hyper-V i VirtualBox, ale funkcjonalno\u015b\u0107 nie spe\u0142ni\u0142a moich wymaga\u0144, wi\u0119c wci\u0105\u017c u\u017cywam tego samego. Okaza\u0142o si\u0119, \u017ce istnieje spos\u00f3b na zintegrowanie VMWare, Dockera i VSCode w jednym \u015brodowisku roboczym.<\/p>\n
Docker Machine<\/b><\/a><\/noindex> \u2014 pozwala uruchamia\u0107 Docker Engine na wirtualnym ho\u015bcie i \u0142\u0105czy\u0107 si\u0119 z nim zar\u00f3wno zdalnie, jak i lokalnie. Dla niego istnieje sterownik zgodno\u015bci z VMWare Workstation, link do GitHuba<\/a><\/noindex><\/p>\n
Nie b\u0119d\u0119 powtarza\u0107 instrukcji instalacji, tylko wypisz\u0119 sk\u0142adniki:<\/p>\n
    \n
  1. Docker Toolbox<\/a><\/noindex> (Docker Machine<\/a><\/noindex> w zestawie)<\/li>\n
  2. Docker Machine VMware Workstation Driver<\/a><\/noindex><\/li>\n
  3. Docker Desktop<\/li>\n<\/ol>\n
    \nTak, Docker Desktop, niestety, r\u00f3wnie\u017c b\u0119dzie potrzebny. Je\u015bli go usuni\u0119to, to instalujemy ponownie, ale tym razem odznaczaj\u0105c pole wyboru dotycz\u0105ce wprowadzania zmian w systemie, aby ponownie nie zepsu\u0107 VMWare Workstation.<\/p>\n
    Od razu chc\u0119 zauwa\u017cy\u0107, \u017ce wszystko dzia\u0142a doskonale z konta zwyk\u0142ego u\u017cytkownika, instalatory poprosz\u0105 o eskalacj\u0119 uprawnie\u0144, gdy b\u0119d\u0105 tego potrzebowa\u0142y, ale wszystkie polecenia w wierszu polece\u0144 i skrypty s\u0105 wykonywane z bie\u017c\u0105cego u\u017cytkownika.<\/i><\/p>\n
    W rezultacie polecenie:<\/p>\n
    $ docker-machine create --driver=vmwareworkstation dev<\/code><\/pre>\n
    \nZ Boot2Docker zostanie utworzona wirtualna maszyna dev, w kt\u00f3rej b\u0119dzie Docker.<\/p>\n
    T\u0119 wirtualn\u0105 maszyn\u0119 mo\u017cna pod\u0142\u0105czy\u0107 do graficznego interfejsu VMWare Workstation, otwieraj\u0105c odpowiedni plik vmx. Nie jest to jednak konieczne, poniewa\u017c VSCode b\u0119dzie teraz wymaga\u0107 uruchomienia skryptu PowerShell (jakim\u015b cudem docker-machine i docker-machine-driver-vmwareworkstation znalaz\u0142y si\u0119 w katalogu bin):<\/p>\n
    cd ~\/bin\n.\/docker-machine env dev | Invoke-Expression\ncode<\/code><\/pre>\n
    \nOtworzy si\u0119 VSCode do pracy z kodem na lokalnej maszynie i Dockerem w wirtualnej maszynie. Wtyczka Docker for Visual Studio Code<\/a><\/noindex> pozwala wygodnie zarz\u0105dza\u0107 kontenerami w wirtualnej maszynie bez zagl\u0105dania do konsoli.<\/p>\n
    Trudno\u015bci:<\/b><\/p>\n
    Podczas tworzenia docker-machine proces u mnie si\u0119 zawiesi\u0142: <\/p>\n
    Waiting for SSH to be available...<\/code><\/pre>\n
    \n\"Docker
    \n
    \nI po pewnym czasie zako\u0144czy\u0142 si\u0119 z przekroczeniem pr\u00f3b nawi\u0105zania po\u0142\u0105czenia z wirtualn\u0105 maszyn\u0105.<\/p>\n
    Ca\u0142a sprawa dotyczy polityki certyfikat\u00f3w. Przy tworzeniu wirtualnej maszyny pojawi si\u0119 katalog ~\/.dockermachinemachinesdev, w kt\u00f3rym b\u0119d\u0105 pliki certyfikat\u00f3w do po\u0142\u0105cze\u0144 SSH: id_rsa, id_rsa.pub. OpenSSH mo\u017ce odmawia\u0107 ich u\u017cycia, poniewa\u017c uwa\u017ca, \u017ce maj\u0105 problemy z prawami dost\u0119pu. Tylko docker-machine nic o tym nie powie, po prostu b\u0119dzie pr\u00f3bowa\u0107 si\u0119 ponownie po\u0142\u0105czy\u0107, a\u017c si\u0119 znudzi.<\/p>\n
    Rozwi\u0105zanie:<\/b> Gdy tylko zacznie si\u0119 tworzenie nowej wirtualnej maszyny, wchodzimy do katalogu ~\/.dockermachinemachinesdev i zmieniamy prawa dost\u0119pu do wskazanych plik\u00f3w, jeden po drugim.<\/p>\n
    W\u0142a\u015bcicielem pliku powinien by\u0107 bie\u017c\u0105cy u\u017cytkownik, a pe\u0142ne prawa powinny mie\u0107 tylko bie\u017c\u0105cy u\u017cytkownik i SYSTEM; wszystkich pozosta\u0142ych u\u017cytkownik\u00f3w, w tym grup\u0119 administrator\u00f3w i samych administrator\u00f3w, nale\u017cy usun\u0105\u0107.<\/p>\n
    Mog\u0105 tak\u017ce wyst\u0105pi\u0107 problemy z konwersj\u0105 absolutnych \u015bcie\u017cek z formatu Windows na Posix oraz z powi\u0105zaniem wolumen\u00f3w zawieraj\u0105cych linki symboliczne. Ale to ju\u017c inna historia.
    \n
    \u0179r\u00f3d\u0142o:     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 i VMWare Workstation na jednej maszynie z Windows | ProHoster","description":"Zadanie by\u0142o proste, zainstalowa\u0107 Docker na moim roboczym laptopie z Windows, na kt\u00f3rym ju\u017c teraz jest chaos.","canonical_url":"https:\/\/prohoster.info\/pl\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pl_PL","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\/pl\/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\/pl\/wp-json\/wp\/v2\/posts\/76494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/comments?post=76494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/posts\/76494\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media\/76495"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/media?parent=76494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/categories?post=76494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pl\/wp-json\/wp\/v2\/tags?post=76494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}