Iggy Jackson

Can confirm the same results as above. In addition, I tested the light sensor using the watch command and could see changes as I covered the sensor.

Looks like a good addition. I'd personally put the definitions below the actual list, but I can see it both ways

I'm using dockerfilelint as part of GitHub's super-linter. Here is a link to it failing as part of that: https://github.com/iggy/scurvy/runs/940683789?check_suite_focus=true#step:4:194 The line it's referencing: https://github.com/iggy/scurvy/blob/master/Dockerfile#L74

Is there precedent for having k0s support an arch for a worker, but not a controller? |Project|Supported?|Relevant Links| |-|-|-| |etcd|not supported|https://github.com/etcd-io/etcd/issues/14522 https://github.com/etcd-io/etcd/pull/14517| |kine|?|No issue or PR| |kube-router|merged, not yet released|https://github.com/cloudnativelabs/kube-router/pull/1525|...

Updated the table above. Both containerd and runc have supported riscv64 for multiple releases.

Is there any easy way to test this with a `k0sctl` cluster? I've managed to get past getting this version uploaded and then get the below error. I can't easily...

Got it. Sounds like I should just do a new cluster. My current cluster is a mix of x86_64 and aarch64 nodes. I have 2 RISC-V boards I could do...

As a note for anyone who runs into this, when using the `uploadBinary` function, you have to have bash installed on the target nodes. The error message you get back...

The `pause` container doesn't support riscv64. I'm trying to track down what would be involved in adding that.

Sorry, just noticed you have a `pause` image at the bottom of your list above. It looks like something is trying to pull the upstream `pause` image. These errors repeat...