mloskot
commented
1 year ago @aravindhp Happy to help, if I can.
The make all is still running for me, so the section title Run in WSL from Windows host filesystem: Success above is not entirely true as it's not completed with success yet i.e. two-node cluster running. I'm updating the output with some Cannot find path failures as you can already see yourself. However, those failures seem not related to the actual issue this PR addresses.
I'm seeing the make all procedure being stuck in loop trying to resolve this issue - it's repeated the same step at least three times already - but as mentioned, this must be a different issue
...
cni: calico
calico: 3.25.0; containerd: 1.6.15
==> winw1: Running provisioner: shell...
winw1: Running: sync/windows/0-containerd.ps1 as C:\tmp\vagrant-shell.ps1
winw1: Stopping ContainerD & Kubelet
winw1: Downloading Calico using ContainerD - [calico: 3.25] [containerd: 1.6.15]
winw1: Installing 7Zip
winw1: Getting ContainerD binaries
winw1: Downloading https://github.com/containerd/containerd/releases/download/v1.6.15/containerd-1.6.15-windows-amd64.tar.gz to C:\Program Files\containerd\containerd.tar.gz
winw1: x containerd-shim-runhcs-v1.exe
winw1: x ctr.exe
winw1: x containerd-stress.exe
winw1: x containerd.exe
winw1: Registering ContainerD as a service
winw1: Starting ContainerD service
winw1: time="2023-04-14T13:23:12.295397500-07:00" level=fatal msg="The specified service already exists."
winw1: Done - please remember to add '--cri-socket "npipe:////./pipe/containerd-containerd"' to your kubeadm join command
==> winw1: Running provisioner: shell...
winw1: Running: sync/windows/forked.ps1 as C:\tmp\vagrant-shell.ps1
winw1:
winw1:
winw1: Directory: C:\
winw1:
winw1:
winw1: Mode LastWriteTime Length Name
winw1: ---- ------------- ------ ----
winw1: d----- 1/21/2022 3:44 AM k
winw1:
winw1:
winw1: cp : Cannot find path 'C:\forked\StartKubelet.ps1' because it does not exist.
winw1: At C:\tmp\vagrant-shell.ps1:11 char:5
winw1: + cp C:/forked/StartKubelet.ps1 c:\k\StartKubelet.ps1
winw1: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
winw1: + CategoryInfo : ObjectNotFound: (C:\forked\StartKubelet.ps1:String) [Copy-Item], ItemNotFoundException
winw1: + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand
winw1:
==> winw1: Running provisioner: shell...
...
aravindhp
jayunit100
adeniyistephen
k8s-ci-robot
Run the cluster from Windows host filesystem. Running it from WSL filesystem is likely to fail.
The current documentation is missing an important requirement for those who want to run the two-node cluster on Windows in WSL environment.
It is important to run
make allinsidesis-windows-dev-toolsrepo cloned on Windows filesystem and not WSL filesystem, and here it is why:Run in WSL from WSL filesystem: Fail
Go to WSL terminal, then run the following sequence:
Run in WSL from Windows host filesystem: Success
Go to WSL terminal, then run the following sequence - notice
F:drive location, not WSL$HOME: