Is it possible to have docker running inside of vmware?
I run vmware workstation for my dev needs and have to maintain different VMs for diff environments.
Docker seems to allow running diff environments in containers, therefore
Inside of my Windows 10 x64 VM can I run docker and use different images and containers to develop, build and test my code? (Remember I'm running my dev envrionment in VMware Workstation while docker uses VirtualBox)
How do I ship/take this my app (code+database+web api+ .....) to production? Does the the production machine need to run docker we well?
Please help clarify.
Update
By VMWare I mean VMWare workstation pro.
windows virtualbox vmware-workstation docker
add a comment |
I run vmware workstation for my dev needs and have to maintain different VMs for diff environments.
Docker seems to allow running diff environments in containers, therefore
Inside of my Windows 10 x64 VM can I run docker and use different images and containers to develop, build and test my code? (Remember I'm running my dev envrionment in VMware Workstation while docker uses VirtualBox)
How do I ship/take this my app (code+database+web api+ .....) to production? Does the the production machine need to run docker we well?
Please help clarify.
Update
By VMWare I mean VMWare workstation pro.
windows virtualbox vmware-workstation docker
add a comment |
I run vmware workstation for my dev needs and have to maintain different VMs for diff environments.
Docker seems to allow running diff environments in containers, therefore
Inside of my Windows 10 x64 VM can I run docker and use different images and containers to develop, build and test my code? (Remember I'm running my dev envrionment in VMware Workstation while docker uses VirtualBox)
How do I ship/take this my app (code+database+web api+ .....) to production? Does the the production machine need to run docker we well?
Please help clarify.
Update
By VMWare I mean VMWare workstation pro.
windows virtualbox vmware-workstation docker
I run vmware workstation for my dev needs and have to maintain different VMs for diff environments.
Docker seems to allow running diff environments in containers, therefore
Inside of my Windows 10 x64 VM can I run docker and use different images and containers to develop, build and test my code? (Remember I'm running my dev envrionment in VMware Workstation while docker uses VirtualBox)
How do I ship/take this my app (code+database+web api+ .....) to production? Does the the production machine need to run docker we well?
Please help clarify.
Update
By VMWare I mean VMWare workstation pro.
windows virtualbox vmware-workstation docker
windows virtualbox vmware-workstation docker
edited Jul 31 '17 at 19:14
fixer1234
18.8k144982
18.8k144982
asked Apr 5 '17 at 10:38
Hamza Ahmed ZiaHamza Ahmed Zia
2041412
2041412
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
Yes, it's entirely possible to run Docker in a VM. Docker is a light virtualization solution, it doesn't virtualize hardware so you won't be affected by problems typical for nested VMs.
Port binding may be a bit tricky though, because you'll have to somehow connect your dev-env VM in VMware with Docker VM in VirtualBox.
You may also run into problems if you want to expose host's folders to a service in a Docker container. Windows' file systems are limited compared to Linux ones in terms of permission granularity and some services don't like that. (this issue is not Docker-specific)
In general, your app isn't locked to Docker in production. Dockerized services communicate with the world through network, no different than what regular services usually do. However, an app designed with Docker (or, more generally, cloud) in mind may be more resilient to failures and easier to maintain.
add a comment |
This blog talks about exactly how to use Docker on Windows with VMWare Workstation. You can even use Windows 7.
https://stefanscherer.github.io/yes-you-can-docker-on-windows-7/
First install the Chocolatey package manager for windows (this is a one-line command)
@"%SystemRoot%System32WindowsPowerShellv1.0powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin"
then install Docker to use VMWare workstation
choco install -y docker
choco install -y docker-machine
choco install -y docker-machine-vmwareworkstation
Create a default vm
docker-machine --native-ssh create -d vmwareworkstation default
Set your environment variables
docker-machine env | iex
Now you are all set to get started.
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")
– Neil
Aug 11 '18 at 15:41
add a comment |
- Yes, you can run docker on Windows. Windows on VMWare also works. We run docker on Linux servers on VMWare.
- The smartest would be to have docker on you production machine also, but it would be possible to copy your data out from the containers. I don't recommend that though.
You can usedocker save
to save your docker images to files.
I think it's worth mentioning that it's not recommended running several applications inside the same container and it's not recommended to store data inside your containers, you should use volumes for that.
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
|
show 1 more comment
There is a major difference between the docker host (Linux or Windows) :
- The Linux host does not need any virtualization technologies
So in Vmware workstation, you can install a standard Linux, then the docker engine and run any containers without problems - The Windows host has a different requirement because under the hood, it creates an Hyper V Linux VM (details in https://rancher.com/the-similarities-and-differences-between-windows-and-linux-containers/)
So on the Windows docker host in a Vmware Workstation (on your physical Windows), you have a nested HyperV Linux VM ! That's not a big issue, just be careful to enable nested virtualization.
François
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1195676%2fis-it-possible-to-have-docker-running-inside-of-vmware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, it's entirely possible to run Docker in a VM. Docker is a light virtualization solution, it doesn't virtualize hardware so you won't be affected by problems typical for nested VMs.
Port binding may be a bit tricky though, because you'll have to somehow connect your dev-env VM in VMware with Docker VM in VirtualBox.
You may also run into problems if you want to expose host's folders to a service in a Docker container. Windows' file systems are limited compared to Linux ones in terms of permission granularity and some services don't like that. (this issue is not Docker-specific)
In general, your app isn't locked to Docker in production. Dockerized services communicate with the world through network, no different than what regular services usually do. However, an app designed with Docker (or, more generally, cloud) in mind may be more resilient to failures and easier to maintain.
add a comment |
Yes, it's entirely possible to run Docker in a VM. Docker is a light virtualization solution, it doesn't virtualize hardware so you won't be affected by problems typical for nested VMs.
Port binding may be a bit tricky though, because you'll have to somehow connect your dev-env VM in VMware with Docker VM in VirtualBox.
You may also run into problems if you want to expose host's folders to a service in a Docker container. Windows' file systems are limited compared to Linux ones in terms of permission granularity and some services don't like that. (this issue is not Docker-specific)
In general, your app isn't locked to Docker in production. Dockerized services communicate with the world through network, no different than what regular services usually do. However, an app designed with Docker (or, more generally, cloud) in mind may be more resilient to failures and easier to maintain.
add a comment |
Yes, it's entirely possible to run Docker in a VM. Docker is a light virtualization solution, it doesn't virtualize hardware so you won't be affected by problems typical for nested VMs.
Port binding may be a bit tricky though, because you'll have to somehow connect your dev-env VM in VMware with Docker VM in VirtualBox.
You may also run into problems if you want to expose host's folders to a service in a Docker container. Windows' file systems are limited compared to Linux ones in terms of permission granularity and some services don't like that. (this issue is not Docker-specific)
In general, your app isn't locked to Docker in production. Dockerized services communicate with the world through network, no different than what regular services usually do. However, an app designed with Docker (or, more generally, cloud) in mind may be more resilient to failures and easier to maintain.
Yes, it's entirely possible to run Docker in a VM. Docker is a light virtualization solution, it doesn't virtualize hardware so you won't be affected by problems typical for nested VMs.
Port binding may be a bit tricky though, because you'll have to somehow connect your dev-env VM in VMware with Docker VM in VirtualBox.
You may also run into problems if you want to expose host's folders to a service in a Docker container. Windows' file systems are limited compared to Linux ones in terms of permission granularity and some services don't like that. (this issue is not Docker-specific)
In general, your app isn't locked to Docker in production. Dockerized services communicate with the world through network, no different than what regular services usually do. However, an app designed with Docker (or, more generally, cloud) in mind may be more resilient to failures and easier to maintain.
answered Apr 5 '17 at 11:02
gronostajgronostaj
28.2k1471107
28.2k1471107
add a comment |
add a comment |
This blog talks about exactly how to use Docker on Windows with VMWare Workstation. You can even use Windows 7.
https://stefanscherer.github.io/yes-you-can-docker-on-windows-7/
First install the Chocolatey package manager for windows (this is a one-line command)
@"%SystemRoot%System32WindowsPowerShellv1.0powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin"
then install Docker to use VMWare workstation
choco install -y docker
choco install -y docker-machine
choco install -y docker-machine-vmwareworkstation
Create a default vm
docker-machine --native-ssh create -d vmwareworkstation default
Set your environment variables
docker-machine env | iex
Now you are all set to get started.
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")
– Neil
Aug 11 '18 at 15:41
add a comment |
This blog talks about exactly how to use Docker on Windows with VMWare Workstation. You can even use Windows 7.
https://stefanscherer.github.io/yes-you-can-docker-on-windows-7/
First install the Chocolatey package manager for windows (this is a one-line command)
@"%SystemRoot%System32WindowsPowerShellv1.0powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin"
then install Docker to use VMWare workstation
choco install -y docker
choco install -y docker-machine
choco install -y docker-machine-vmwareworkstation
Create a default vm
docker-machine --native-ssh create -d vmwareworkstation default
Set your environment variables
docker-machine env | iex
Now you are all set to get started.
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")
– Neil
Aug 11 '18 at 15:41
add a comment |
This blog talks about exactly how to use Docker on Windows with VMWare Workstation. You can even use Windows 7.
https://stefanscherer.github.io/yes-you-can-docker-on-windows-7/
First install the Chocolatey package manager for windows (this is a one-line command)
@"%SystemRoot%System32WindowsPowerShellv1.0powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin"
then install Docker to use VMWare workstation
choco install -y docker
choco install -y docker-machine
choco install -y docker-machine-vmwareworkstation
Create a default vm
docker-machine --native-ssh create -d vmwareworkstation default
Set your environment variables
docker-machine env | iex
Now you are all set to get started.
This blog talks about exactly how to use Docker on Windows with VMWare Workstation. You can even use Windows 7.
https://stefanscherer.github.io/yes-you-can-docker-on-windows-7/
First install the Chocolatey package manager for windows (this is a one-line command)
@"%SystemRoot%System32WindowsPowerShellv1.0powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%chocolateybin"
then install Docker to use VMWare workstation
choco install -y docker
choco install -y docker-machine
choco install -y docker-machine-vmwareworkstation
Create a default vm
docker-machine --native-ssh create -d vmwareworkstation default
Set your environment variables
docker-machine env | iex
Now you are all set to get started.
edited Jan 9 at 23:53
Waclock
1033
1033
answered Jul 15 '17 at 16:11
steampoweredsteampowered
1,13382740
1,13382740
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")
– Neil
Aug 11 '18 at 15:41
add a comment |
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")
– Neil
Aug 11 '18 at 15:41
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Excellent! Thanks for sharing this. PS: The last line is for PowerShell, without "| iex" that would work in cmd
– Dmitry Gusarov
Mar 6 '18 at 7:45
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
Chocolatey was new to me, this was a nice starting point: hanselman.com/blog/…
– ccook
Apr 11 '18 at 18:14
1
1
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:
docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")– Neil
Aug 11 '18 at 15:41
Just in case anyone else tried this without reading the link the "Create a default vm" command should be:
docker-machine --native-ssh create -d vmwareworkstation default
(Note missing "-")– Neil
Aug 11 '18 at 15:41
add a comment |
- Yes, you can run docker on Windows. Windows on VMWare also works. We run docker on Linux servers on VMWare.
- The smartest would be to have docker on you production machine also, but it would be possible to copy your data out from the containers. I don't recommend that though.
You can usedocker save
to save your docker images to files.
I think it's worth mentioning that it's not recommended running several applications inside the same container and it's not recommended to store data inside your containers, you should use volumes for that.
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
|
show 1 more comment
- Yes, you can run docker on Windows. Windows on VMWare also works. We run docker on Linux servers on VMWare.
- The smartest would be to have docker on you production machine also, but it would be possible to copy your data out from the containers. I don't recommend that though.
You can usedocker save
to save your docker images to files.
I think it's worth mentioning that it's not recommended running several applications inside the same container and it's not recommended to store data inside your containers, you should use volumes for that.
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
|
show 1 more comment
- Yes, you can run docker on Windows. Windows on VMWare also works. We run docker on Linux servers on VMWare.
- The smartest would be to have docker on you production machine also, but it would be possible to copy your data out from the containers. I don't recommend that though.
You can usedocker save
to save your docker images to files.
I think it's worth mentioning that it's not recommended running several applications inside the same container and it's not recommended to store data inside your containers, you should use volumes for that.
- Yes, you can run docker on Windows. Windows on VMWare also works. We run docker on Linux servers on VMWare.
- The smartest would be to have docker on you production machine also, but it would be possible to copy your data out from the containers. I don't recommend that though.
You can usedocker save
to save your docker images to files.
I think it's worth mentioning that it's not recommended running several applications inside the same container and it's not recommended to store data inside your containers, you should use volumes for that.
answered Apr 5 '17 at 10:51
Mikael KjærMikael Kjær
1,200313
1,200313
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
|
show 1 more comment
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
Thanks for your answer but please clarify You said"Windows on VMWare also works" but did you mean "Docker on VMWare also works"?
– Hamza Ahmed Zia
Apr 5 '17 at 10:56
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@HamzaAhmedZia "VMWare" What exactly? ESXi? Workstation? Be specific and edit your question. Workstation only exists on Linux and Windows.
– Ramhound
Apr 5 '17 at 10:57
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@Ramhound I mean Workstation. Updated question
– Hamza Ahmed Zia
Apr 5 '17 at 10:59
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@HamzaAhmedZia so in the context of Workstation, the author of this answer indicates, that you can run Docker within a Windows VMWare Workstation VM.
– Ramhound
Apr 5 '17 at 11:00
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
@Mikael What is your recommendation for shipping to production since you say you do not recommend to copy data out from the containers?
– Hamza Ahmed Zia
Apr 5 '17 at 11:03
|
show 1 more comment
There is a major difference between the docker host (Linux or Windows) :
- The Linux host does not need any virtualization technologies
So in Vmware workstation, you can install a standard Linux, then the docker engine and run any containers without problems - The Windows host has a different requirement because under the hood, it creates an Hyper V Linux VM (details in https://rancher.com/the-similarities-and-differences-between-windows-and-linux-containers/)
So on the Windows docker host in a Vmware Workstation (on your physical Windows), you have a nested HyperV Linux VM ! That's not a big issue, just be careful to enable nested virtualization.
François
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
add a comment |
There is a major difference between the docker host (Linux or Windows) :
- The Linux host does not need any virtualization technologies
So in Vmware workstation, you can install a standard Linux, then the docker engine and run any containers without problems - The Windows host has a different requirement because under the hood, it creates an Hyper V Linux VM (details in https://rancher.com/the-similarities-and-differences-between-windows-and-linux-containers/)
So on the Windows docker host in a Vmware Workstation (on your physical Windows), you have a nested HyperV Linux VM ! That's not a big issue, just be careful to enable nested virtualization.
François
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
add a comment |
There is a major difference between the docker host (Linux or Windows) :
- The Linux host does not need any virtualization technologies
So in Vmware workstation, you can install a standard Linux, then the docker engine and run any containers without problems - The Windows host has a different requirement because under the hood, it creates an Hyper V Linux VM (details in https://rancher.com/the-similarities-and-differences-between-windows-and-linux-containers/)
So on the Windows docker host in a Vmware Workstation (on your physical Windows), you have a nested HyperV Linux VM ! That's not a big issue, just be careful to enable nested virtualization.
François
There is a major difference between the docker host (Linux or Windows) :
- The Linux host does not need any virtualization technologies
So in Vmware workstation, you can install a standard Linux, then the docker engine and run any containers without problems - The Windows host has a different requirement because under the hood, it creates an Hyper V Linux VM (details in https://rancher.com/the-similarities-and-differences-between-windows-and-linux-containers/)
So on the Windows docker host in a Vmware Workstation (on your physical Windows), you have a nested HyperV Linux VM ! That's not a big issue, just be careful to enable nested virtualization.
François
answered May 6 '18 at 1:19
François YACOBFrançois YACOB
1
1
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
add a comment |
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
That point about Windows hosting a HyperV VM is incorrect if running Docker for Windows in Windows Container mode and using LCoW side-by-side. It has other problems, but the linked articles stance about the agnosticism of Docker based on host OS is short-sighted at best based on where Moby Project is heading with Windows container based docker on Win 10. But I just sank a week into discovering that the bleeding edge is still drawing blood, and not backed down to the danger level of only leading-edge. At this point it looks like another six months until it is ready as a daily driver.
– Tetsujin no Oni
May 22 '18 at 4:22
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1195676%2fis-it-possible-to-have-docker-running-inside-of-vmware%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown