Due to the license issues with docker desktop and the fact that you don't really need this buggy bit of software, this guide will walk you through the steps to use VSCode+remote-containers in combination with WSL2 without using docker desktop.
Only if you have docker desktop currently installed of course
Via app & features in the windows settings menu
in windows cmd.exe:
wsl --unregister docker-desktop-data
wsl --unregister docker-desktopIf you were using the docker CLI in WSL2 that came with Docker Desktp let's get rid of all traces of that
rm -rf ~/.docker
sudo rm -rf /usr/local/lib/dockerIn theory you should also be able to sunstitute docker with podman, but I haven't tried that. Here are the instructions for using docker-ce, based roughly on this guide: https://docs.docker.com/engine/install/ubuntu/
Add the docker package registry with pre-built binaries
sudo apt-get update
sudo apt-get install \
ca-certificates \
curl \
gnupg \
lsb-release
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/nullInstall docker deamon and CLI
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.ioAdd a groupp docker and add yourself so you can run docker without sudo:
sudo groupadd docker
sudo gpasswd -a $USER dockerBase on https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-compose-on-ubuntu-20-04 To be hones I am a bit lost as what goes where exacly, so will accpet suggestions/improvements. This is what worked for me.
# create directory for plugins
mkdir $HOME/.docker
mkdir $HOME/.docker/cli-plugins
# install docker-compose v2.2.3, see https://github.com/docker/compose/releases for latest
sudo curl -L "https://github.com/docker/compose/releases/download/v2.2.3/docker-compose-linux-x86_64" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
docker-compose --version
# create symbolic link in plugins directory
ln -s /usr/local/bin/docker-compose $HOME/.docker/cli-plugins/docker-compose
# install buildx v0.7.1, see https://github.com/docker/buildx/releases for latest
sudo curl -L "https://github.com/docker/buildx/releases/download/v0.7.1/buildx-v0.7.1.linux-amd64" -o $HOME/.docker/cli-plugins/docker-buildx
sudo chmod +x $HOME/.docker/cli-plugins/docker-buildxThere are multiple ways to accomplish this, see also:
I tried this and it sems to work adequately. Note that I user ZSH as terminal, if you use bash, you will need to modify .bashrc instead of .zshrc
Based on https://blog.nillsf.com/index.php/2020/06/29/how-to-automatically-start-the-docker-daemon-on-wsl2/
# Allow docker to be started without requesting sudo password:
sudo visudo
# add line
<your user name> ALL=(ALL) NOPASSWD: /usr/bin/dockerd
# add docker stuff to ~/.zshrc
echo '# Start Docker daemon automatically when logging in if not running.' >> ~/.zshrc
echo 'RUNNING=`ps aux | grep dockerd | grep -v grep`' >> ~/.zshrc
echo 'if [ -z "$RUNNING" ]; then' >> ~/.zshrc
echo ' sudo dockerd > /dev/null 2>&1 &' >> ~/.zshrc
echo ' disown' >> ~/.zshrc
echo 'fi' >> ~/.zshrcAfter this, finally docker should work, you can check with this test image
>> sudo docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:975f4b14f326b05db86e16de00144f9c12257553bba9484fed41f9b6f2257800
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
...
To enable docker buildkit you need to set DOCKER_BUILDKIT=1. However if you set that in ~/.zshrc this doesn't get loaded when VSCode calls docker. So we use the WSLENV variable like so:
- Add
DOCKER_BUILDKIT=1to your windows environmental variables - set/append
DOCKER_BUILDKIT/u:to theWSLENVvariable Now every WSL instance will have theDOCKER_BUILDKITvariable set
From WSL2, log into docker
echo $CONTAINER_REGISTRY_PASSWORD | docker login -u $CONTAINER_REGISTRY_USERNAME --password-stdin $CONTAINER_REGISTRYMake sure you have these extensions installed in vscode:
- ms-vscode-remote.remote-wsl
- ms-vscode-remote.remote-containers
Open WSL, and open vscode from there (use code . to open vscode in the current folder). In the lower left corner it should say WSL, to indicate that WSL is running from inside your WSL environment.
If you get an error message like Docker returned an error code ENOENT, message: ... you have most likely tried to open a folder on your windows drive in containers. With docker desktop this is possbile (but a bad idea giving bad performance), but with this setup it is not possible as there is not docker client installed in Windows, and that is how we want it. Make sure to move your projects to the wsl dirve (accessible as \\wsl$\Ubuntu\home from windows)
thanks for the detail explain
After installation, I can make docker-compose up and ran, mount host folders no issue, run terminal and script within docker has no issue, but can not use : "Attach Visual Studio Code", message: "cannot attache to the container with name/id/python, it no longer exists"
any help is welcome