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
Related
Closed. This question is not about programming or software development. 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 days ago.
Improve this question
can't run docker run command and docker desktop is stopped...
i tried reinstalling and upgraded wsl 1 to 2
Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": open //./pipe/docker_engine: The system cannot find the file specified. See 'docker run --help'.
The error suggests that docker is not running or properly installed, if you installed it, check the following.
From the search bar, type "Turn Windows features on or off" and make sure you enable the following:
Windows subsystem for Linux
virtual machine platform
windows hypervisor platform
You may also check the PATH of the docker if it is properly added in the environment variable.
From the search bar type "Edit the system environment variable" then click on "Environment variable" in the bottom right corner then under the System variable section choose "path" in the "variable" column then "edit"
A new window will open. Make sure that the following path is added
C:\Program Files\Docker\Docker\resources\bin
If you have done all these steps. You should make sure that the docker desktop app is running, then try to run docker commands.
If the problem still persists, you may uninstall the app and reinstall it again and it should work
Closed. This question is not about programming or software development. 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 6 months ago.
Improve this question
I can't get Docker to start on my Mac (Intel). It's just stuck in Docker Desktop starting...
Here are the things I have tried:
Running with the desktop installer
Running with the brew installer (brew install --cask docker)
In the debug menu:
Clean /Purge data
Reset to factory defaults
Trying to run docker ps in terminal shows:
Error response from daemon: dial unix docker.raw.sock: connect: no such file or directory
If I quit docker, the com.docker.vmnetd process needs to be killed manually.
This problem started around version 4.5.0 Now I am on version 4.12.0., and still the same issue. If I downgrade to a version far back (with the previous UI), it works. But after a while, Docker forces itself to update, which puts me back in this same problem.
Does anyone have any clue what I can try?
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 1 year ago.
Improve this question
I have a client who sent me instructions to connect to their VPN, but their VPN solution is only supported on Windows. Therefore, I'm trying to use Windows inside of VirtualBox to install Docker, so that I can pull down a container (Kali) to perform my assessment.
However, I've spent a little over 7 hours today troubleshooting. I'm trying to figure out what's wrong with either Windows or my configuration settings. I've gone from installing Windows Server 2019 in Amazon's EC2, Lightsail, Windows 10 in VMware Fusion, and now finally VirtualBox. No luck. Each of the solutions requires a lot of hacking and troubleshooting to figure out what's going on.
Host specs:
macOS Big Sur
2.9GHz Quad Core Intel Core i7Memory: 16GB
Storage: 500GB flash storage
I've allocated 4GB of memory to the host, along with 2 processor cores.
As you can see in the screenshot below, Windows 10 Pro is telling me that I need to enable something, which the Optional Features window on the left shows is enabled. As you can also see on the right hand side, I have hardware virtualization enabled in the VM.
It's literally the same thing documented here: https://www.configserverfirewall.com/windows-10/please-enable-the-virtual-machine-platform-windows-feature-and-ensure-virtualization-is-enabled-in-the-bios/
Here's all the things that I've tried thus far:
Attempt #1 (re: https://github.com/microsoft/WSL/issues/5363#issuecomment-640337948)
dism /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
bcdedit /set hypervisorlaunchtype auto
Here's the output:
After rebooting and trying to fire up Docker again, the same error occurs.
Attempt 2: Checking BIOS
Several have suggested doing this, but I have found no way to boot into the Windows BIOS using VirtualBox. Nothing here.
Attempt 3: Re-enabling WSL (re: https://github.com/microsoft/WSL/issues/5363#issuecomment-675786863)
Per the instructions in this comment, I have disabled WSL from the Optional Features section in Windows 10, rebooted, got an error about WSL 2 not being enabled, re-enabled WSL, rebooted again, and just ran into the exact same error.
Attempt 4: Disabled Hyper-V
Disabled Hyper-V and got the same error.
Attempt 5: Modifying the .VMX file (re: https://communities.vmware.com/t5/VMware-Fusion-Discussions/VMware-Fusion-12-1-0-Big-Sur-Host-Windows-10-Guest-Running-Slow/td-p/2814913)
However, no luck here either. Instead of the previous error, it fails with "The operation timed out because a response was not received from the virtual machine or container". I guess it got even slower.
Any new suggestions or pointers on how to resolve this?
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.