Which Intel virtualizaton techniques are necessary for Docker? - virtualization

Which Intel virtualizaton techniques are necessary for Docker?
On a Linux system running on a Intel cpu, what Virtualization Technologies by Intel are necessary to fullfill the execution of a Docker container? E.g. there are VT-X, ...
Or is there no need of using such a technology because Docker is somehow different to existing virtualization solutions like VirtualBox. In this case, why is there no need?

None. Docker uses a completely different system - it's not running a virtual machine so much as a super chroot. See the question below:
Can I run Docker directly on a non VT-X machine (no Virtual Machine used)?
The tutorials that tell you you'll need VT-x are usually based on running docker in Windows (on Hyper-V) or in VirtualBox.

Related

Kubernetes in docker for Ubuntu

Is there an ubuntu version of Kubernetes in docker for Ubuntu, that works like docker for mac(https://blog.docker.com/2018/01/docker-mac-kubernetes/).
and docker for windows (https://docs.docker.com/docker-for-windows/#kubernetes)
minikube consumes lots of resource, and I want to try out a lighter alternative, which I found docker for mac that supports kubernetes, but my machine is ubuntu 18.04.
As you may know there are a lot of projects that offer K8S solution, Minikube is the closest to an official mini distribution for local testing and development, but if you wanna try lightweight options you can check:
Kind runs Kubernetes clusters in Docker containers. It supports multi-node clusters as well as HA clusters. Because it runs K8s in Docker, kind can run on Windows, Mac, and Linux. Kind may not have developer-friendly features.
K3s is ma project by Rancher as a lightweight Kubernetes offering suitable for edge environments, IoT devices, CI pipelines, and even ARM devices, like Raspberry Pi's. It runs on any Linux distribution without any additional external dependencies or tools. K3s provides lightweight by replacing docker with containerd, and using sqlite3 as the default DB (instead of etcd). This solution consumes 512 MB of RAM and 200 MB of disk space.
K3d
It is based on a k3s which is a lightweight kubernetes distribution (similar to kind).
Microk8s runs upstream Kubernetes as native services on Linux systems supporting snap. A good option if you are running Ubuntu on your Laptop. There is a very good installation tutorial:
And there are plenty more. You can check what solution suits you best.
Check kind it is kubernetes in docker.

Docker microsoft/nanoserver won't start

I have a problem with Docker running the nanoserver.
My environment: I Installed docker on a Win10 (developer build from microsoft) Virtual Machine (cause host is still Win7 with no default Docker support because of Hyper-V). I installed docker on the virgin image so no 3rd-party programs can cause the error. I also have already checked if Hyper-V is enabled.
But I think this Screenshot says everything:
Also Googled the problem, but everything i found wasn't in a Docker context.
FYI: I want to use the Docker container for running a network rendering slave which should only see one cpu core (for licensing reasons), maybe someone has another option for this.
so you are trying to run Docker on Windows 10 which is a VM on Windows 7? I suppose this is not possible. You are trying to run a virtualization platform inside a virtualized Host (your Windows 10 machine). This nested virtualization is not supported by Windows 7 afaik.
Nested virtualization is supported on Windows 10 Build 10565 and later (this must be your virtualization host).
Have you tried to create and run a Hyper-V VM inside that Windows 10 VM? this will also fail.

Why Xen requires an OS though it is a Type I Hypervisor?

Xen is a Type I hypervisor that means it can run directly on hardware so why do we need to install Ubuntu or CentOS or any OS to run Xen? It should run directly on the hardware as it's a Type I hypervisor.
The reason that an OS is needed is because Xen itself does not directly provide any mechanism for creating/managing virtual machines. Because these tasks require things like creating disk images, editing configuration files, setting up networking etc. It would be wasteful for the Xen project to reimplement all of this functionality when it is already included in widely-used OSes like Linux.
The only way to interact with Xen is by making hypercalls, some of which can only be made from the dom0 (Domain 0) VM. As noted in the Xen wiki this means that the hypervisor can be left to just the tasks which only it can perform - checking page tables, allocating resources for new domains, and scheduling domains.
I'm not aware of any type 1 hypervisor which does not need an OS in one way or another - many of them use Xen under the hood, with a custom OS. Things like VMWare ESXi (which does not use Xen) bundle their own OS as part of the distribution so still have an OS running on top of the hypervisor to provide needed functionality.

Does Revirtualization works with Hyper-V and not Xen

I was installing vagrant with virtualbox provision. When I am running it on Amazon EC2, then it doesn't work saying:
* Running VirtualBox in a Xen environment is not supported
EC2 uses xen virtualization. On the other hand, its working fine on Windows Azure Virtual Machines which uses a customized version of Hyper-V.
So,cant we use virtualbox in Xen but in Hyper-V?
Are you sure that HyperV allow you to start the VM, I don't think this is possible using current hardware VT technology without slow painful emulation instead of virtualization.

Xen for office use and network boot

I'm trying to understand if Xen can fit my needs:
I need to have a Windows 7 image that I can copy to different machines (with different hardware) to have kind of default installation for every new entry in the office and faster replacement.
Is that possible to use the hypervisor for this?
Is that possible to use network boot as well of the hypervisor not to install Xen on every machine?
Edit: Will I be able tu use multiple displays?
Thanks.
It is possible if and only if you have installed Xen on every machine on your network that is not a good idea. Xen and other type-1 hypervisors are usually used to multiplex a high-end server into a set of virtual machines. Xen is also known for its para-virtualization technique which is not applicable for Windows.
Have you ever thought of VDI (Virtual Desktop Infrastructure) solutions? It enables you to have all your operating systems on a single machine and transfer the desktop to the clients.