I've installed docker on windows 10 machine. When I start it I get error
As it can be seen on the picture below, I have Hyper-V switched on as on in the windows features, so not sure what is wrong. Anyone can advise please?
I am not sure about the issue. I did face same issue on my desktop than I switched from Hyper-V to WSL 2. and it worked. Below link could be useful for you.
Docker for Windows-WSL
Related
I'm on windows 10 and I'm encountering Docker on Windows crashing on startup.
I just installed docker on windows and have a couple of containers spinning up (last night). I've been able to use it but after reboot, or shutdown, this was the behaviour ever since. Pretty unstable.
It looks like this and terminates after a while without any prompt of an error.
More info that I have Hyper-V installed on my machine and "Use the WSL 2 based engine" option enabled on docker.
On my end, I was able to solve this by:
Going to Apps & Features
Search for Ubuntu (or any linux distro you've installed)
Click on it and navigate to Advance options
Click on Reset button.
Also, try to trial and error which docker on windows version is stable with your system.
Hope that helps.
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
I am currently attempting to run a macOS High Sierra VM on my Windows 10 laptop using VMWare Workstation 12 Player.
To make the VM work, it says I must disable Hyper-V - Upon disabling, the VM does indeed work.
However, when I want to run Docker on my macOSHS VM, it gives the error:
There is also a link to a page telling one how to work with Hyper-V and that it should be re-toggled to work, along with some CMD code that I can't seem to get to work...
When I turn off Hyper-V the VM starts as normal, but when I try to install/run Docker on there... I am greeted with:
Has anybody run into this problem before?
Follow this answer, basically you have to enable virtualization in the vmware settings in the processor tab.
https://serverfault.com/questions/841330/docker-on-mac-on-vmware/849836#849836
I've been playing around with Docker in the past few weeks and currently I'm trying to set up a project.
I'm running a Raspberry Pi with Docker installed. I want to set up a container and use RDP to connect to a remote host.
I have tried working with Xorg (LXDE) and tried starting my graphical environment with startx but that doesn't seem to work. After some googling I found out that you cannot run startx on a virtualized device since startx will look after the graphics card and a virtual machine does not have that.
In order for my RDP to work I need a GUI that runs in a Docker container and uses the ARM architecture.
Has anyone else had any experience with this?
All help is appreciated!
Thanks
Vincentvo
Adding --privileged to my docker run command fixed my issue.
Just curious, but are you 100% tied to RDP? If you use VNC, you could just use the ubuntu ARM distro and then VNC into it. IF you are using a windows machine, superVNC should work for you.
There are even VNC clients for android. Come to think of it, you might be able to use Chrome RDP as well, havent tried that though.
Trying to solve my problem I did the next:
Added 'Ubuntu_64' to config file.
Switched my WiFi off (saw this solution at Laravel forums) before 'vagrant up' execution.
Enabled GUI.
Rolled the VirtualBox and its extension back (also from Laravel forums).
The VMs which were successfully run with Vagrant are the Debian Wheezy 7.5 x32 built with puphpet and precise32.
As we can see, only x32 VMs could be run on my machine. I don't know why.
Here is my machine info:
OS: Ubuntu 12.04 64
Processor: AMD A8-4500M, 2 cores
Virtualization is enabled in BIOS. See screenshot similar to my BIOS view: screenshot
The latest Vagrant, VirtualBox and VirtualBox Extensions pack are installed
my user is added to virtualbox group
Thanks in advance.
Dude, your question helped me to fix my problem!
I was getting this connection timeout, turned my wifi off and bam! All working fine!
Double check if your ubuntu is really 64 bit.
I got some problems with some linux architectures for AMD in the pest!
There are a few and sometimes they can be a headache.. I think I got this problem with centos, it was i686 instead of simple x64. I don't really know the difference but what you can try doing is:
Instead of adding the homestead box (vagrant box add laravel/homestead)
Why dont you try adding a simple ubuntu-32 machine and then you run vagrant up.
I dont really know if it's going to work, but it's worth trying!
Thanks again for your answer, it really helped me