Reset fails to unmount/unlink /var/lib/k0s on alpine

```log
time="2023-10-06T08:41:06Z" level=debug msg="[ssh] 127.0.0.1:9023: resetting k0s..."
time="2023-10-06T08:41:06Z" level=debug msg="[ssh] 127.0.0.1:9023: executing `/usr/local/bin/k0s reset --data-dir=/var/lib/k0s`"
time="2023-10-06T08:41:07Z" level=debug msg="[ssh] 127.0.0.1:9023: (stderr) time=\"2023-10-06 08:41:07\" level=warning msg=\"failed to unmount /var/lib/k0s\""
time="2023-10-06T08:41:07Z" level=debug msg="[ssh] 127.0.0.1:9023: (stderr) time=\"2023-10-06 08:41:07\" level=warning msg=\"To ensure a full reset, a node reboot is recommended.\""
time="2023-10-06T08:41:07Z" level=debug msg="[ssh] 127.0.0.1:9023: (stderr) Error: errors received during clean-up: [failed to delete /var/lib/k0s. err: unlinkat /var/lib/k0s: device or resource busy]"
time="2023-10-06T08:41:07Z" level=debug msg="[ssh] 127.0.0.1:9023: k0s reset failed: "
time="2023-10-06T08:41:07Z" level=warning msg="[ssh] 127.0.0.1:9023: k0s reported failure: command failed: client exec: ssh session wait: Process exited with status 1"
```

Could be a k0s issue

Start with the reported `k0s reset --data-dir=/var/lib/k0s` command and compare cleanup behavior on Alpine. Trace the unmount and deletion failure for `/var/lib/k0s`; done means reset completes without the device-or-resource-busy error and no reboot is required.

Written by the indexing model from the issue text.