search

rancher-sandbox / rancher-desktop-wsl-distro

Minimal WSL distro for Rancher Desktop
Apache License 2.0
16 stars 8 forks source link

Bump Alpine to 3.19 and switch to openresty 0.0.2 to prefix the package name #83

Closed jandubois closed 10 months ago

jandubois commented 10 months ago

Jan says there are issues with k3s and cgroupsv2.

That was with Alpine 3.19 on Lima (macOS); I haven't tested it on Windows yet, where this might be controlled by WSL2 instead.

We shouldn't merge this until

Yes, will turn into draft for now.

jandubois commented 10 months ago

I think this PR is ready for review/merging now. It passes [E2E tests on Windows] (https://github.com/rancher-sandbox/rancher-desktop/actions/runs/7702707188/job/20991555355?pr=6373) and continues to support k3d as before:

C:\Users\SUSE\AppData\Local\rancher-desktop\logs>k3d cluster create
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-k3s-default'
INFO[0000] Created image volume k3d-k3s-default-images
INFO[0000] Starting new tools node...
INFO[0001] Creating node 'k3d-k3s-default-server-0'
INFO[0012] Pulling image 'docker.io/rancher/k3s:v1.27.4-k3s1'
INFO[0015] Pulling image 'ghcr.io/k3d-io/k3d-tools:5.6.0'
INFO[0024] Creating LoadBalancer 'k3d-k3s-default-serverlb'
INFO[0024] Starting Node 'k3d-k3s-default-tools'
INFO[0039] Pulling image 'ghcr.io/k3d-io/k3d-proxy:5.6.0'
INFO[0063] Using the k3d-tools node to gather environment information
INFO[0063] HostIP: using network gateway 172.19.0.1 address
INFO[0063] Starting cluster 'k3s-default'
INFO[0063] Starting servers...
INFO[0063] Starting Node 'k3d-k3s-default-server-0'
INFO[0068] All agents already running.
                                                        INFO[0068] Starting helpers...
                                                                                                                INFO[0069] Starting Node 'k3d-k3s-default-serverlb'
                                                INFO[0075] Injecting records for hostAliases (incl. host.k3d.internal) and for 2 network members into CoreDNS configmap...
                                                   INFO[0077] Cluster 'k3s-default' created successfully!
                                                                                                           INFO[0077] You can now use it like this:
                                           kubectl cluster-info

C:\Users\SUSE\AppData\Local\rancher-desktop\logs>kubectl get no
NAME                       STATUS   ROLES                  AGE   VERSION
k3d-k3s-default-server-0   Ready    control-plane,master   18s   v1.27.4+k3s1

(yes, the wonky formatting of the latter log lines looked like this in the terminal too)