Anyone seen this issue before? This is the error I get if I go to my system tray -> Right click on the Docker icon -> try to create a Dev environment. I can create Linux containers just fine.
Related
I am new to Docker and trying to set it up on my Windows 10 machine. I installed Docker Desktop but when I run it, I get this "Docker desktop stopping..." message rightaway and Docker doesn't seem to start. What am I doing wrong?
I had the same probably using Windows. To fix it, I had to make sure WSL 2 was installed properly:
https://learn.microsoft.com/en-gb/windows/wsl/install-manual#step-4---download-the-linux-kernel-update-package
If it's already installed on your machine, try uninstalling and reinstalling it.
However, I can see that people have already mentioned that solution. If you've done it and it didn't work, try this as well:
Open Docker Desktop and click on the 'troubleshoot' icon in the top right corner. Click 'Clean/Purge Data' and select 'WSL 2' only and click 'delete'. Then restart your machine and it should work. Hope that helps!
I am trying to learn Docker and have installed it on my laptop. I have tried to uninstall it and delete the Docker directory as Administrator, but keep getting the error message "The action cannot be completed because the file is open in Docker Desktop service". But Docker Desktop Service is not open, and does not appear whenever I open Task Manager. When I try to reinstall Docker, it says it it up to date, when clearly it is not. I would appreciate any help getting a fresh installation of Docker.
Here is the Docker directory C:\Program Files\Docker\Docker.
Here is the error message.
If you have access to the windows machine, through UI, you can:
Go to Start -> Services, and search for the Docker (probably is called Docker Desktop or something similar) service and
Manually Stop. You can also set the service to start Manually, not Automatically, give a restart and
Now Docker is completely stopped and
You can uninstall safely.
User azbarcea answered the question.
I want to do demonstrate to the IT area at my work how one might use a container for isolated development. I have installed WSL2, then I have a development container running with some basic developer tools--OpenJDK, etc. I can SSH into the container from a WSL2 terminal simply by running ssh user#172.17.0.2, for example, but I cannot figure out how to SSH into this from Windows. More importantly, I want to be able to SSH into the running container from Visual Studio Code via Windows, but things just seem to time out. Does anybody know how to get this going? I have a very locked-down IT environment and I want to do this without having to install Docker for Windows (which I doubt my IT department will ever approve).
I am trying to develop in a remote container.
I run VS Code on my local windows machine.
I have a linux machine which runs docker and a bunch of containers.
I have the "Remote - Containers" and "Remote - SSH" extensions installed in VS Code.
I can connect to my linux machine in VS Code and I can see the running containers.
I can right click on a container and choose "Attach Shell". This works fine:
When I right click on a container and choose "Attach Visual Studio Code" I get an error:
UPDATE
The above error was raised because (for some reason?) docker must be running locally on windows also even though we are fully on a remote machine. I've installed and run docker locally.
Now when I right click on a running container, I get a different error:
Of course the containers are running -- I see them.
How can I Attach Visual Studio Code to a running remote container successfully?
This may not be a real answer but it's too much for a comment.
I believe you have a local machine and docker on a remote server.
The first thing you have to do is to install docker on your local machine and configure it so that's its looking for the docker host on your remote server.
Then you can create a .devcontainer.json on your machine. If you have the extension installed, VSCode will offer you do open this as container environment. Since your docker host sits on remote, this will now happen on your server instead of your local machine.
When I did the setup, I followed amongst other things this guide. Especially the SSH-Agent was required to get a remote docker host working. https://code.visualstudio.com/docs/remote/containers-advanced#_a-basic-remote-example
Here is a example .devcontainer file of mine.
Now back to your initial question, I don't think you will be able to use the remote container extension on a container that wasn't started as dev container. This is because vscode will install a bunch of stuff in there when its first set up. Similar to the SSH Extension. I may be wrong on this so take it with a grain of salt.
It may also be worth noting that once you connect to your server via SSH and have then the regular docker extension (which is not the remote container extension) installed, on remote, you will see your docker images listed there. But that does not mean you will be able to connect like that from local to remote container. For that you need to configure a docker remote host.
I have also faced similar issue after doing some research I found the issue was with my installation.
But I faced this issue when I installed vs-code through snap in Ubuntu.
May be try uninstalling VS Code and reinstalling it.
It should work if Docker is installed properly.
I have installed Docker for Windows (running Windows 10). Out of the box, Docker would not install an image on Hyper-V but I was able to get it work.
Edit: I acquired Kitematic via the link from this screen:
Upon clicking download, I get a zip file via http.
Next, I copied Kitematic zip contents to c:\program files\docker\kitematic. When I run Kitematic from Docker menu, it gives me an error stating:
VirtualBox is not installed. Please install it via the Docker Toolbox.
I don't want to use VirtualBox, if at all possible because I have other software that uses Hyper-V.
Is it possible to get Kitematic to use Hyper-V?
Thanks,
You only need to delete Kitematic folder in %APPDATA% (C:\Users\{User}\AppData\Roaming) and run Kitematic again.
Next scenario worked for me:
disable hyper-v feature in windows
reinstall docker toolbox with Kitematic
reboot PC
run Kitematic
got to Settings -> uncheck "use virtualbox instead of native on next restart"
enable hyper-v back
restart PC
start Docker for windows
run Kitematic
Some of these steps may be redundant but it helped in my case.
I believe there must be some file or setting to tell Kitematic to use hyper-V instead of virtualbox provider but I wasn't managed to find another way of changing it.