Using Docker on Windows10 Home WSL2

Author's environment

• Windows10 Home
• WSL( ubuntu 18.04)
• CPU: core i-7
• RAM: 16GB
• Docker for windows

Introduction

In Windows 10 Pro, Hyper-V is installed by default, so you can easily build an environment using Docker desktop for windows, but in Windows 10 Home that does not have Hyper-V, building docker is a little troublesome.

Therefore, there are several ways to use docker under Windows 10 Home environment.

1. Launch docker using WSL (Windows Subsystem for Linux)
2. Launch docker on VB using Vagrant

This time, we will set up the first method using WSL, which has a fast initial execution speed and few steps to build a development environment.

Launch docker using WSL

Advance preparation

1. ** Install WSL2. ** ** Install WSL2 so that you can access OS such as ubuntu from Windows OS. The installation procedure of WSL2 is omitted here, but ** WSL2 ** is installed instead of WSL1.

2. ** Install Docker desktop for Windows ** Install Dokcer desktop for Windows (https://docs.docker.com/docker-for-windows/install/) on your Windows machine

3. ** Install docker, docker-compose ** Install the latest version of docker and docker-compose on ubuntu of WSL2. Reference: https://qiita.com/tettsu__/items/85c96850d187e4386c24

procedure

1. WSL2 settings

For some reason, in Docker desktop for Windows using WSL2, it is not possible to operate the allocation of CPU etc. from the setting screen, so Change the CPU / memory / SWAP / disk size from the terminal.

2. Docker desktop for windows settings

What we do is make the docker daemon on WSL2 available on Docker desktop for Windows.

ʻUse the WSL2 based engine` ✔

ʻEnable integration with my default WSL distro`.

If ubuntu is installed on WSL2 and set correctly, a message like "Ubuntu" will appear as shown in the above picture, so turn it on.

** [Note] ** If you cannot check the ✔ column above,

--tcp: // localhost: 2375 cannot be set. (Forgot to export the localhost path to bashrc) --You are using WSL1 instead of WSL2

Such causes are possible. (Please google for details)

3. Create a project in ubuntu terminal on WSL2.

Create a project in ubuntu terminal (hereinafter referred to as ubuntu terminal) on WSL2.

ubuntu:~ $ mkdir work
ubuntu:~ $ cd work
ubuntu:~/work $ git clone [email protected]/~

** [Points to note] **

--Generally, you can access the Windows directory from the ubuntu terminal using / mnt / c, This time, create a project in the Windows directory, and instead of referencing it from the ubuntu terminal, ** create the project directly in the directory on ubuntu. ** ** (When docker is launched in a project on a Windows directory, it takes a tremendous amount of time to access the disk, and it takes about 5 minutes from launching docker to displaying the initial screen. I stumbled here.)

3. docker-compose up

Open ubuntu terminal and launch docker container.

$ docker-compose up -d

With this, it is ok if you start the container without throwing an error, It wasn't that easy in my environment, so here are the errors I faced and their solutions.

Errors in environment construction and their solutions

case 1: sh I can't find the file!

error

ERROR: for rails_1  Cannot start service rails: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"bin/start_dev_server.sh\": stat bin/start_dev_server.sh: no such file or directory": unknown

** Occurrence procedure **

1. Create a project under / mnt / c
2. docker-compose up

** Cause ** In this case, the root of the absolute path of WSL2 is / mnt / c, This was because the Docker for Windows VM applied the root of the absolute path of / C.

solution Create a project under the Windows directory, stop referencing it, and create a project under the ubuntu directory.

** Reference link **

• https://github.com/microsoft/WSL/issues/1854#

case 2: I can't access AWS S3!

error

Aws::S3::Errors::RequestTimeTooSkewed: The difference between the request time and the current time is too large.

** Occurrence procedure **

1. docker-compose up
2. Error fetching masked data from AWS S3

** Cause ** The cause was that the time of the Docker container running on WSL2 (ubuntu terminal) was significantly different.

Windows host side (correct)

$ data 
Sun Aug 30 18:16:29 JST 2020

ubuntu terminal side

$ data
Sun Aug 28 11:16:29 JST 2020

solution

1. First, set the timezone to JST in docker-compose.yml, because the ʻAws :: S3 :: Errors :: RequestTimeTooSkewed` error will occur even if the Timezone is different.

docker-compose.yml

services:
  web: 
   environment:
     TZ: Asia/Tokyo

2. Next, First, when using the data command in the shell of the container, it is necessary to set the authority so that operation is not permitted.

docker-compose.yml

services:
  web:
   privileged: true

3. Finally, In the container's shell, use the data command to change the date

$ data --set "2020-08-30 18:16:29" //Manually set to the current time

** Memo ** Besides, it seems that you can change the time by using hwclock -s, but you will die with the following error.

$ hwclock -s
hwclock: Cannot access the Hardware Clock via any known method.

** Reference link **

• https://qiita.com/sadakan5/items/4c0a394fd1d6be34efb2

case 3: docker-daemon is not connected!

error

$ docker-compose up
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.

** Occurrence procedure **

1. docker-compose up

** Cause ** The cause I understand is

1. Another VM is running The virtual machine platform used when using docker, which runs on the Hyper-V platform (which is different from <-Hyper-V) (although this is very annoying), and other virtual machines such as Oracle Virual Box. It seems that using them at the same time is not good because it causes a conflict of Hyper-V platform (?). --Reference link: https://qiita.com/matarillo/items/ca1eecf8f9a3cd76f9ce

2. WSL is not enabled

I think there are many other causes as well.

solution For cause 1 --Stop other VMs

• Reboot

For cause 2

--Open PowerShell and

Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

Reference link: https://qiita.com/aki4000/items/c26e3076c8cec9677415

Other

Time required to display the initial screen (speculation)

--Opt 1 [WSL2]: When launching docker of the project under ubuntu directory using WSL2 introduced this time

• Opt 2 [WSL2 in /mnt/cproject]: As mentioned above, when using WSL2 to launch docker for a project under a Windows directory

--Opt 3 [Vagrant]: When docker is launched on the VM using Vagrant

** Time from accessing localhost to displaying the top page after launching the docker container ⇓ **

I want to edit the project under ubuntu dire with IDE such as RubyMine

For projects under Windows Dire, you can usually open RubyMine or VS code and edit it, Viewing ubuntu dire from a Windows terminal is a bit tedious, and editing a project under ubuntu dire using an IDE is a bit confusing.

procedure

1. Install Vcxsrv and set it to Yoshina
2. Install Rubymine from ubuntu terminal
3. Start Xlaunch obtained by Vcxsrv and start rubymine.sh.