Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Docker allows the host Linux distribution to be different from the guest Linux distribution.
Are there limits to this compatibility? Could you run a recent Ubuntu guest in a host whose kernel is much older?
Docker allows the host Linux distribution to be different from the guest Linux distribution.
To make things clear, there is no guest Linux distribution when running a Docker container. The Docker container is not a Linux OS.
Docker images such as ubuntu, centos, ... are not operating systems. They are just images that "mimic" an OS distribution from the point that they have a very similar filesystem structure and tools available
that you typically find on an OS distro like Ubuntu or Centos. Those images do not have their own kernel packaged inside.
If you are wondering whether you can run the Docker image ubuntu:16.04 on a machine with ubuntu:14.04 the answer is yes. In addition, there shouldn't be any compatibility problems in general with other images.
Now since the kernel is not part of the image, it is possible to create a Docker image that would work on one kernel version and fail on another. For instance, you can request a system call that might not exist
in an older kernel version.
However, this problem is not caused by docker, but rather is a compatibility issue with the software running inside the container.
Finally, if you are running Docker on a machine you will at minimum have a kernel version of 3.10 which is not very old. So it is unlikely to encounter any such limitations.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I knew that docker won't work on windows 10 home edition. It will work in windows 10 pro or enterprise as it need hyper v and it is available in these two. But I found some script for hyper v and able to install and enable hyper v in window 10 home. So is it better to install ubuntu as a virtual environment and install docker over there. or the windows 10 home with hyper v enabled will be good enough to install docker.
Please help me to understand this.
Thanks.
Docker does work on Windows 10 home (I'm using it now).
Install Docker Desktop (wsl2 integration will be disabled)
Install wsl 2.0
Restart.
Install your distro of choice through the Microsoft Store (I used Ubuntu).
Initialise Ubuntu and configure your user account.
If you run Docker in Ubuntu at this point you'll see a request to integrate with wsl2, open the Docker Desktop settings and enable integration with WSL2 for your linux distribution.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
When I try to run a downgraded cuda version on the container this happens.
Can I use a downgraded Cuda version on the Container and another cuda version of the host machine?
Yes, you can.
When you specify to docker --gpus all (or some variant of that switch) you are using the GPU-enabled version of docker (which is recommended, if you are using GPUs).
When properly set up, that docker GPU enablement should allow you to run a version of CUDA that is less than or equal to the CUDA (driver API) version that is reported by nvidia-smi.
In your case, nvidia-smi is reporting support for up to CUDA version 11.1, and that means you can pull/run/use a docker container that is based on CUDA 10.0, for example (as is the case in your example.)
There don't appear to be any problems in the output you have shown.
The CUDA toolkit version you have installed on the base machine is irrelevant for what is being used in the container, but the CUDA driver version (which is what is reported by nvidia-smi will dictate the latest CUDA toolkit version you can use, whether in the container, or on the base machine. But the CUDA toolkit in the base machine and the CUDA toolkit in the container do not interact, and have no relevance to each other.
Only the GPU driver version (i.e. the CUDA version supported by the GPU driver installed on the base machine) matters for compatibility.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
How does one install docker for Windows Server 2008?
I only see support for Windows Server 2016:
https://www.docker.com/docker-windows-server
Docker for Windows https://www.docker.com/docker-windows only works on Windows 10 Pro/2016.
For all other windows versions you must use Docker Toolbox
https://docs.docker.com/toolbox/toolbox_install_windows/. A subtle but important difference.
Docker Toolbox comes with the ominous warning:
Legacy desktop solution. Docker Toolbox is for older Mac and Windows systems that do not meet the requirements of Docker for Mac
and Docker for Windows. We recommend updating to the newer
applications, if possible.
So I guess this is not getting maintained anymore and may disappear.
You can install it with "Docker Toolbox for Windows" from here: Official Source
I had problem in installation but finally installed properly with these catches:
Hyper V must be enabled (wasn't possible when I was trying in windows server hosted in another VM, had to switch)
It was telling that virtualbox has error so it cannot continue :/ Solved it by uninstalling docker, virtualbox both, then removed all vbox* .dll files from c:\windows\system32\drivers folder. Afterwards when re-installed again, it worked.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I have a two part question:
first is that can anyone please tell me the command lines to execute in docker to start building a container and vm?
second is i have already built a VM using docker but the problem is whenever the building of VM reaches the stage where it written WAITING FOR VM TO BOOT it's stuck there and the error of HYPERVISOR IS NOT RUNNING comes even when the HYPER-V MACHINE MANAGEMENT is on automatic and running.
So please, help me get rid of this problem.
To create a VM which will run docker, use docker-machine: copy docker-machine-Windows-x86_64.exe as docker-machine.exe anywhere you want.
docker-machine create -d virtualbox
docker-machine start
But Make sure you have removed the Windows feature HyperV, as it is not compatible with VirtualBox/VMWare.
Or use the Hyper-V driver. You have to chose one or the other.
See "Getting Docker running on Windows 10"
as it turns out, HyperV and VirtualBox will not run together side-by-side in 64 bit modes. And Scott's blog post about rebooting to a hypervisorlaunchtype off mode of Windows 8.1 worked flawlessly for Windows 10.
So I didn't have to un-install the HyperV feature, but as it turns out, I did have to disable HyperV
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm planning to try out Docker for a toy project, and since I'm on Mac OS X, I need to run it on a VM. I also plan to deploy this on a VPS, with hopefully the same OS. Is it a good idea to use CoreOS as the container host OS, or should I just stick with a more popular distribution like Ubuntu?
I don't really plan to do clustering anytime soon, so I'm wondering if CoreOS would add unnecessary complexity. It seems to me that you can ignore etcd or just use it locally if you want (with the benefit of possibly scaling later on), but I'm not absolutely certain on that.
You can boot CoreOS with all of the default settings and have a fully working Docker host out of the box. All of the clustering features will not be running unless specifically enabled.
One benefit of using CoreOS as a docker host is that (if you use systemd functionality) the systemd journal lets you do things like tail output of your container without having to run a bunch of docker logs commands.
https://coreos.com/docs/cluster-management/debugging/reading-the-system-log/#tail-the-journal