I am working onto install Minikube on Azure VM - Ubuntu - NV6.
I installed KVM2 driver, now as mentioned in the document it is required t have VT-x/AMD-v virtualization enabled in BIOS .
Question - How do i know if Azure VM - NV6 supports VT-x/AMD-v virtualization ? If it not by default, how can i enable it?
I also installed Minikube using curl, but it throws error if i try to start Minikube.
Any help would be much appreciated.
There are an on going issue on GitHub, will track it there.
https://github.com/kubernetes/minikube/issues/4730#issue-466395657
https://github.com/kubernetes/minikube/issues/4804#issue-469709296
Thanks
Related
i need some help for installing kyma locally.
I was following the official guide:
https://kyma-project.io/docs/kyma/latest/04-operation-guides/operations/02-install-kyma/
I have:
Windows 10
Hyper-V activated
Docker Desktop installed (v4.9.1)
Kubernetes (1.24.0) - shown by kubectl version --client
K3d (v5.4.3)
kyma-cli 2.0.4
kubernetes-helm 3.8.2
I installed it like this:
Starting up Docker Desktop
kyma provision k3d
kyma deploy
While deploying now, i get some errors, which tell me, that some essential components can not be deployed:
Errors
Can you help me solve this so that i can start up a functional kyma instance?
Greetings and thanks in advance!
The issue was the kubernetes version. After downgrading my docker desktop to 4.1, which is using kubernetes 1.21 it works now.
As of version 1.20, Kubernetes deprecated Docker as a container runtime in favor of containerd. Due to a different way in which containerd handles certificate authorities, Kyma's built-in Docker registry does not work correctly on clusters running with a self-signed TLS certificate on top of Kubernetes installation where containerd is used as a container runtime.
If that is your case, either upgrade the cluster to use Docker instead of containerd, generate a valid TLS certificate for your Kyma instance or configure an external Docker registry.
another way is to disable kubernetes provided by docker-desktop and use the command below to provision kubernetes cluster based on k3d
kyma provision k3d
I'm trying to setup a local development environment on a linux machine. The ideal setup would be using a docker container spinning up the server with a shared directory to push code changes.
The question is if this is an accepted approach to use? Any tips appreciated.
There is
a public guide how to setup an environment on ICM 7.9 , https://support.intershop.com/kb/index.php/Display/28K663, and
a sample linux VM on ICM 7.5.5. provided in case you have got a support login - https://support.intershop.com/static/Customer-Support-offers-a-Linux-VM-as-an-example--development-environment-for-Intershop-7.5.html
but both of them are not related to a docker container, however it may help you with settung up a development environment in there.
I have a large container that I cannot get via network (due to shitty internet connection), so I need a way to export that container to hard drive in order to use it on my Windows machine. So basically:
Docker container running on Linux ->
Export/Save on hard drive ->
Import/Load on Windows ->
Run on Windows 10 with/without Hyper-V?
How can I achieve this? I'm confused about Export/Import and Load/Save? Can you give full command line commands?
Let's assume this is my container:
Container ID: 638aac32ff06
Image: registry.mycompany.com/db:latest
Ports: 0.0.0.0:5432->5432/tcp
Name: db
You can't. Containers are created under Linux won't work under clear Windows. I hope in the future when MS will make complite release Ubuntu subsystem under Windows it will be possible. But not now.
Yes, it seems possible now! (which is quite amazing!)
On Linux (source machine) run:
docker save {container_name} -o {path_to_save}.tar
Then, on Windows (target machine) run:
docker load -i {path_to_save}.tar
That's all! (Be sure docker desktop is set to use Linux containers from tray icon menu)
I am getting an error upon installing docker on azure virtual machine.
m/c configuration: azure vm, windows 10 enterprise, Intel 2.4 GHz, 7 GB RAM, 64-bit operating system, x64-based processor.
I went through a few blogs and they asked me to enable nested virtualization on azure vm as follows.
Set-VMProcessor -VMName MobyLinuxVM -ExposeVirtualizationExtensions $true
But this also didn't help and the virtual m/c MobyLinuxVM failed to start.
I have installed Hyper-V and Container components from windows features. But the error shows "because one of the Hyper-V components is not running" whereas all the components of Hyper-V are running.
I checked the task manager performance tab and I don't see the virtualization option there. I can't modify the virtualization settings in the BIOS as I am installing docker on an Azure VM. Also I tried disabling the windows firewall but that didn't help.
So how to run docker on azure virtual m/c windows 10 enterprise.
Here is a solution if you are getting this error on Azure Windows 10 VM where you have installed Docker:
Ensure Windows Hyper-V featutes are enabled by running PowerShell cmdlet:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All -Verbose
Ensure Windows Containers feature is enabled by running PowerShell cmdlet:
Enable-WindowsOptionalFeature -Online -FeatureName Containers -All -Verbose
Ensure Hypervisor is set to auto start in the Boot Configuration Database (BCD) by running in elevated command prompt the command:
bcdedit /set hypervisorlaunchtype Auto
After running all of the above and you restart the Azure VM, Docker should be starting normally.
Azure doesnt yet allow for nested virtualization.
You need to use DSv3 or E3 instances for that. Just use docker like you normally would
Microsoft offers images with preinstalled docker enterprise. This works even on a B2s VM. Just select any of the "Microsoft Server 2019/2016 Datacenter with containers" image while creating the VM.
I have followed this (IIS Windows Container) https://hub.docker.com/r/microsoft/iis/ and am running into this (Not authorised) https://github.com/docker/docker/issues/21558 is it just me? Am i doing something wrong? Or does this just not work yet?
I'm running Windows 10 (Build 14931) in VM Ware with Docker beta 1.12.2-Beta28
ps I don't have enough rep to create windows-containers as a tag...
No the Docker image is fine on Win10 - you may be hitting the loopback problem, where you can't connect via localhost or 127.0.0.1 because of a limitation in the Windows network stack.
Try this:
docker run -d -p 80:80 --name iis microsoft/iis
docker inspect --format '{{ .NetworkSettings.Networks.nat.IPAddress }}' iis
The second line will give you the NAT IP address of the container, and you should be able to browse to http://{container-ip} and see the IIS welcome page.
Incidentally, if you're using the VM just to work with Docker, you'd be better off using Windows Server 2016 - you can use Windows Server Containers instead of Hyper-V Containers, and they're quite a bit faster to start.
For future me / people having the same issue. Firstly definitely follow Elton's advice the links provided make for a much better dockerfile / experience when building the container. However the issue (for me) was that I don't think I was copying / adding the files to the build. {Oops} Still not clear what magic is done on the Nerd-dinner clone so that it imports the correct files but that gav e the hint I needed
https://github.com/sixeyed/nerd-dinner/blob/dockerize-part1/docker/Dockerfile
https://blog.sixeyed.com/windows-dockerfiles-and-the-backtick-backslash-backlash/