{"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\/lv\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","title":{"rendered":"Docker un VMWare Workstation uz viena Windows datora","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Uzdevums bija vienk\u0101r\u0161s, uzst\u0101d\u012bt Docker sav\u0101 darba kl\u0113pjdator\u0101 ar Windows, kur\u0101 jau t\u0101pat bija zood\u0101rzs. Uzst\u0101d\u012bju Docker Desktop, izveidoju konteinerus, viss k\u0101rt\u012bb\u0101, bet \u0101tri paman\u012bju, ka VMWare Workstation vairs nesp\u0113j palaist virtu\u0101l\u0101s ma\u0161\u012bnas ar k\u013c\u016bdu:<\/p>\n

VMware Workstation un Device\/Credential Guard nav savietojami. VMware Workstation var palaist, p\u0113c Device\/Credential Guard atsl\u0113g\u0161anas.<\/code><\/pre>\n
\n<\/a><\/noindex><\/p>\n
Darbs apst\u0101j\u0101s, nepiecie\u0161ams steidzami labot<\/h3>\n
\n\"Docker
\n
\nMekl\u0113jot ar Google, noskaidroju, ka \u0161\u012b k\u013c\u016bda rodas nesavietojam\u012bbas d\u0113\u013c starp VMWare Workstation un Hyper-V vien\u0101 dator\u0101. Problema ir zin\u0101ma un ir ofici\u0101ls VMware risin\u0101jums, k\u0101 to salabot<\/a><\/noindex>, ar atsauci uz Microsoft zin\u0101\u0161anu b\u0101zi P\u0101rvald\u012bt Windows Defender Credential Guard<\/a><\/noindex>. Risin\u0101jums ir atsl\u0113gt Defender Credential Guard (man pal\u012bdz\u0113ja 4. punkts sada\u013c\u0101 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
\nP\u0113c Windows restart\u0113\u0161anas, t\u0101 jaut\u0101s, vai tie\u0161\u0101m v\u0113laties atsl\u0113gt Defender Credential Guard. J\u0101! T\u0101d\u0113j\u0101di VMWare Workstation atgriez\u012bsies norm\u0101l\u0101 darb\u012bb\u0101, un m\u0113s non\u0101ksim taj\u0101 pa\u0161\u0101 viet\u0101, kur bij\u0101m pirms Docker uzst\u0101d\u012b\u0161anas.<\/p>\n
Risin\u0101jumu, k\u0101 samierin\u0101t Hyper-V un VMWare Workstation, es t\u0101 ar\u012b neatradu, ceru, ka jaunaj\u0101s versij\u0101s t\u0101s sadraudz\u0113sies. <\/p>\n
Cits ce\u013c\u0161<\/h3>\n
\nEs jau sen lietoju VMWare Workstation da\u017e\u0101diem m\u0113r\u0137iem, m\u0113\u0123in\u0101ju p\u0101riet uz Hyper-V un VirtualBox, bet funkcionalit\u0101te neapmierin\u0101ja manas vajadz\u012bbas, t\u0101p\u0113c joproj\u0101m turpinu to lietot. Izr\u0101d\u012bj\u0101s, ka ir risin\u0101jums, k\u0101 savienot VMWare, Docker un VSCode vien\u0101 darba vid\u0113.<\/p>\n
Docker Machine<\/b><\/a><\/noindex> \u2014 \u013cauj palaist Docker Engine uz virtu\u0101l\u0101 hosta un piek\u013c\u016bt tam gan att\u0101lin\u0101ti, gan lok\u0101li. Un tam ir sader\u012bbas draiveris ar VMWare Workstation, saite uz GitHub<\/a><\/noindex><\/p>\n
Uzst\u0101d\u012b\u0161anas instrukciju \u012bpa\u0161i neizst\u0101st\u012b\u0161u, tikai sast\u0101vda\u013cu saraksts:<\/p>\n
    \n
  1. Docker Toolbox<\/a><\/noindex> (Docker Machine<\/a><\/noindex> iek\u013cauts komplekt\u0101)<\/li>\n
  2. Docker Machine VMware Workstation Driver<\/a><\/noindex><\/li>\n
  3. Docker Desktop<\/li>\n<\/ol>\n
    \nJ\u0101, Docker Desktop, diem\u017e\u0113l, ar\u012b b\u016bs nepiecie\u0161ams. Ja to esat izdz\u0113su\u0161i, uzst\u0101d\u0101m no jauna, bet \u0161oreiz no\u0146emot atz\u012bmi par izmai\u0146u veik\u0161anu oper\u0113t\u0101jsist\u0113m\u0101, lai atk\u0101rtoti nesaboj\u0101tu VMWare Workstation.<\/p>\n
    Vispirms v\u0113los nor\u0101d\u012bt, ka viss lieliski darbojas no parast\u0101 lietot\u0101ja puses, instal\u0101cijas programmas l\u016bgs ties\u012bbu paaugstin\u0101\u0161anu, kad tas b\u016bs nepiecie\u0161ams, bet visas komandas komandu rind\u0101 un skripti tiek izpild\u012bti no pa\u0161reiz\u0113j\u0101 lietot\u0101ja.<\/i><\/p>\n
    Rezult\u0101t\u0101 ar komandu:<\/p>\n
    $ docker-machine create --driver=vmwareworkstation dev<\/code><\/pre>\n
    \ntiks izveidota virtu\u0101l\u0101 ma\u0161\u012bna dev Boot2Docker iek\u0161ien\u0113, kur\u0101 b\u016bs Docker.<\/p>\n
    \u0160o virtu\u0101lo ma\u0161\u012bnu var pievienot grafiskaj\u0101 interfeis\u0101 VMWare Workstation, atverot attiec\u012bgo vmx failu. Tom\u0113r tas nav oblig\u0101ti, jo tagad VSCode b\u016bs j\u0101s\u0101k ar PowerShell skriptu (man kaut k\u0101 docker-machine un docker-machine-driver-vmwareworkstation izr\u0101d\u012bj\u0101s tie\u0161i bin map\u0113):<\/p>\n
    cd ~\/bin\n.\/docker-machine env dev | Invoke-Expression\ncode<\/code><\/pre>\n
    \nAtv\u0113rsies VSCode, lai str\u0101d\u0101tu ar kodu uz lok\u0101l\u0101s ma\u0161\u012bnas un Docker virtu\u0101laj\u0101 ma\u0161\u012bn\u0101. Piesaist\u012btais Docker for Visual Studio Code<\/a><\/noindex> pied\u0101v\u0101 \u0113rti p\u0101rvald\u012bt konteinerus virtu\u0101laj\u0101 ma\u0161\u012bn\u0101, neiespie\u017eoties konsol\u0113.<\/p>\n
    Gr\u016bt\u012bbas:<\/b><\/p>\n
    Izveidojot docker-machine, man process iestr\u0113ga: <\/p>\n
    Waiting for SSH to be available...<\/code><\/pre>\n
    \n\"Docker
    \n
    \nUn p\u0113c k\u0101da laika tas pabeidz\u0101s ar p\u0101rsniegt\u0101m savienojuma izveido\u0161anas m\u0113\u0123in\u0101jumu reiz\u0113m ar virtu\u0101lo ma\u0161\u012bnu.<\/p>\n
    Visa lieta ir sertifik\u0101tu politik\u0101. Izveidojot virtu\u0101lo ma\u0161\u012bnu, jums par\u0101d\u012bsies katalogs ~\/.dockermachinemachinesdev, kur\u0101 b\u016bs sertifik\u0101tu faili SSH piek\u013cuvei: id_rsa, id_rsa.pub. OpenSSH var atteikties tos izmantot, jo uzskata, ka tiem ir piek\u013cuves ties\u012bbu probl\u0113mas. Tikai docker-machine jums par to neko neteiks, bet vienk\u0101r\u0161i turpin\u0101s p\u0101rbaud\u012bt savienojumu, l\u012bdz tas apn\u012bk.<\/p>\n
    Risin\u0101jums:<\/b> Kad s\u0101ksies jaunas virtu\u0101l\u0101s ma\u0161\u012bnas izveide, ieejiet katalog\u0101 ~\/.dockermachinemachinesdev un mainiet ties\u012bbas uz min\u0113tajiem failiem, pa vienam.<\/p>\n
    Faila \u012bpa\u0161niekam j\u0101b\u016bt pa\u0161reiz\u0113jam lietot\u0101jam, piln\u012bg\u0101m ties\u012bb\u0101m tikai pa\u0161reiz\u0113jam lietot\u0101jam un SYSTEM, visiem p\u0101r\u0113jiem lietot\u0101jiem, ieskaitot administratoru grupu un pa\u0161iem administratoriem, j\u0101izn\u012bcina.<\/p>\n
    T\u0101pat var rasties probl\u0113mas ar absol\u016bto ce\u013cu konvert\u0113\u0161anu no Windows form\u0101ta uz Posix, un ar sai\u0161u apjomu piesaist\u012b\u0161anu, kas satur simbolisk\u0101s saites. Bet tas jau ir cits st\u0101sts.
    \n
    Avots:     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\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 un VMWare Workstation uz vienas Windows ma\u0161\u012bnas | ProHoster","description":"Uzdevums bija vienk\u0101r\u0161s: uzst\u0101d\u012bt Docker uz sava darba portat\u012bv\u0101 datora ar Windows, uz kura jau ir dz\u012bvnieku zoolo\u0123ija.","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\/lv\/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\/lv\/wp-json\/wp\/v2\/posts\/76494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=76494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/76494\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/76495"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=76494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=76494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=76494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}