{"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\/pt\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","title":{"rendered":"Docker e VMWare Workstation em uma \u00fanica m\u00e1quina Windows.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

A tarefa era simples, instalar o Docker no meu laptop de trabalho com Windows, que j\u00e1 estava cheio de coisas. Instalei o Docker Desktop, criei cont\u00eaineres, tudo certo, mas logo descobri que o VMWare Workstation parou de iniciar as m\u00e1quinas virtuais com um erro:<\/p>\n

O VMware Workstation e o Device\/Credential Guard n\u00e3o s\u00e3o compat\u00edveis. O VMware Workstation pode ser executado ap\u00f3s desativar o Device\/Credential Guard.<\/code><\/pre>\n
\n<\/a><\/noindex><\/p>\n
O trabalho parou, preciso consertar isso urgentemente<\/h3>\n
\n\"Docker
\n
\nAtrav\u00e9s de uma pesquisa no Google, descobri que esse erro ocorre devido \u00e0 incompatibilidade entre o VMWare Workstation e o Hyper-V em uma mesma m\u00e1quina. O problema \u00e9 conhecido e existe uma solu\u00e7\u00e3o oficial da VMWare para isso consertar<\/a><\/noindex>, com um link para a base de conhecimento da Microsoft Gerenciar o Windows Defender Credential Guard<\/a><\/noindex>. A solu\u00e7\u00e3o consiste em desativar o Defender Credential Guard (a se\u00e7\u00e3o 4 do cap\u00edtulo Desativar o Windows Defender Credential Guard me ajudou):<\/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
\nAp\u00f3s reiniciar, o Windows perguntar\u00e1 se voc\u00ea realmente deseja desativar o Defender Credential Guard. Sim! Assim, o VMWare Workstation voltar\u00e1 a funcionar normalmente, e estaremos na mesma situa\u00e7\u00e3o de antes da instala\u00e7\u00e3o do Docker.<\/p>\n
N\u00e3o consegui encontrar solu\u00e7\u00f5es para como conciliar o Hyper-V e o VMWare Workstation; espero que em novas vers\u00f5es eles consigam se entender. <\/p>\n
Outra solu\u00e7\u00e3o<\/h3>\n
\nJ\u00e1 faz tempo que estou usando o VMWare Workstation para diversos fins; tentei mudar para o Hyper-V e VirtualBox, mas suas funcionalidades n\u00e3o atenderam \u00e0s minhas necessidades, ent\u00e3o continuo com o VMWare at\u00e9 hoje. Descobri que existe uma solu\u00e7\u00e3o para integrar o VMWare, Docker e VSCode em um \u00fanico ambiente de trabalho.<\/p>\n
Docker Machine<\/b><\/a><\/noindex> \u2014 permite executar o Docker Engine em um host virtual e se conectar a ele tanto remotamente quanto localmente. E existe um driver de compatibilidade com o VMWare Workstation, link para o GitHub<\/a><\/noindex><\/p>\n
N\u00e3o vou detalhar o guia de instala\u00e7\u00e3o, apenas a lista de ingredientes:<\/p>\n
    \n
  1. Docker Toolbox<\/a><\/noindex> (Docker Machine<\/a><\/noindex> inclu\u00eddo)<\/li>\n
  2. Docker Machine VMware Workstation Driver<\/a><\/noindex><\/li>\n
  3. Docker Desktop<\/li>\n<\/ol>\n
    \nSim, o Docker Desktop, infelizmente, tamb\u00e9m ser\u00e1 necess\u00e1rio. Se voc\u00ea o desinstalou, instale-o novamente, mas desta vez desmarcando a op\u00e7\u00e3o de fazer altera\u00e7\u00f5es no SO, para n\u00e3o quebrar o VMWare Workstation novamente.<\/p>\n
    Quero ressaltar que tudo funciona perfeitamente com um usu\u00e1rio padr\u00e3o; os instaladores solicitar\u00e3o eleva\u00e7\u00e3o de privil\u00e9gios quando necess\u00e1rio, mas todos os comandos no prompt de comando e scripts s\u00e3o executados com o usu\u00e1rio atual.<\/i><\/p>\n
    No final, o comando \u00e9:<\/p>\n
    $ docker-machine create --driver=vmwareworkstation dev<\/code><\/pre>\n
    \nUma m\u00e1quina virtual dev ser\u00e1 criada a partir do Boot2Docker, que conter\u00e1 o Docker.<\/p>\n
    Essa m\u00e1quina virtual pode ser anexada \u00e0 interface gr\u00e1fica do VMWare Workstation, abrindo o respectivo arquivo vmx. Mas isso n\u00e3o \u00e9 obrigat\u00f3rio, pois agora ser\u00e1 necess\u00e1rio iniciar o VSCode com um script do PowerShell (por algum motivo, o docker-machine e o docker-machine-driver-vmwareworkstation acabaram na pasta bin):<\/p>\n
    cd ~\/bin\n.\/docker-machine env dev | Invoke-Expression\ncode<\/code><\/pre>\n
    \nO VSCode ser\u00e1 aberto para trabalhar com o c\u00f3digo na m\u00e1quina local e o Docker na m\u00e1quina virtual. O plugin Docker for Visual Studio Code<\/a><\/noindex> permite gerenciar containers na m\u00e1quina virtual sem precisar ir ao console.<\/p>\n
    Desafios:<\/b><\/p>\n
    Durante o processo de cria\u00e7\u00e3o do docker-machine, tive um travamento: <\/p>\n
    Waiting for SSH to be available...<\/code><\/pre>\n
    \n\"Docker
    \n
    \nAp\u00f3s algum tempo, a tentativa de conex\u00e3o com a m\u00e1quina virtual ultrapassou o limite.<\/p>\n
    O problema est\u00e1 na pol\u00edtica de certificados. Ao criar a m\u00e1quina virtual, voc\u00ea ter\u00e1 um diret\u00f3rio ~\/.dockermachinemachinesdev onde estar\u00e3o os arquivos de certificado para conex\u00e3o via SSH: id_rsa, id_rsa.pub. O OpenSSH pode se recusar a us\u00e1-los, pois considera que h\u00e1 problemas com as permiss\u00f5es. No entanto, o docker-machine n\u00e3o informa nada sobre isso, apenas tenta se reconectar at\u00e9 se cansar.<\/p>\n
    Solu\u00e7\u00e3o:<\/b> Assim que a cria\u00e7\u00e3o de uma nova m\u00e1quina virtual come\u00e7ar, acesse o diret\u00f3rio ~\/.dockermachinemachinesdev e altere as permiss\u00f5es dos arquivos, um a um.<\/p>\n
    O propriet\u00e1rio do arquivo deve ser o usu\u00e1rio atual, o acesso completo deve ser apenas do usu\u00e1rio atual e do SYSTEM, todos os outros usu\u00e1rios, incluindo o grupo de administradores e os pr\u00f3prios administradores devem ser removidos.<\/p>\n
    Tamb\u00e9m podem surgir problemas com a convers\u00e3o de caminhos absolutos do formato Windows para Posix, e com a montagem de volumes que cont\u00eam links simb\u00f3licos. Mas essa j\u00e1 \u00e9 outra hist\u00f3ria.
    \n
    Fonte:     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 e VMWare Workstation em uma mesma m\u00e1quina Windows | ProHoster","description":"A tarefa era simples, instalar o Docker no meu laptop de trabalho com Windows, que j\u00e1 tinha um verdadeiro zool\u00f3gico de configura\u00e7\u00f5es.","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/administrirovanie\/docker-i-vmware-workstation-na-odnoj-windows-mashine","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","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\/pt\/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\/pt\/wp-json\/wp\/v2\/posts\/76494","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=76494"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/76494\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media\/76495"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=76494"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=76494"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=76494"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}