Pascal van Dam

Can confirm same issue is on 1.12.2; K8S 1.25.2, ARM/PI4 architecture

relay logs: ``` level=info msg="Starting gRPC server..." options="{peerTarget:hubble-peer.kube-system.svc.cluster.local:443 dialTimeout:5000000000 retryTimeout:30000000000 listenAddress::4245 metricsListenAddress: log:0x400037c2a0 serverTLSConfig: insecureServer:true clientTLSConfig:0x40000acbe8 clusterName:default insecureClient:false observerOptions:[0xbfc7d0 0xbfc8d0] grpcMetrics: grpcUnaryInterceptors:[] grpcStreamInterceptors:[]}" subsys=hubble-relay level=warning msg="Failed to create peer client...

Logs of backend container in UI: ``` level=info msg="running hubble status checker\n" subsys=ui-backend level=info msg="fetching hubble flows: connecting to hubble-relay (attempt #1)\n" subsys=ui-backend level=info msg="hubble-relay grpc client created (hubble-relay addr:...

But still is doesn´t work (yet): ``` 2023/03/05 21:05:03 Publishing quay.io/pamvdam/containers-57bcbf1d2df6010d41816c012905835d:latest 2023/03/05 21:05:04 existing blob: sha256:21219c3231f5a1cca4febbaf40f698b78e04a2d2860b65346ccd1c7db0ef2e92 2023/03/05 21:05:05 pushed blob: sha256:b339feae942b1dcc6edb5974d16f82c7c719464e6b41bf2561c1800c57291a06 Error: failed to publish images: error publishing ko://containers: writing...

Same issue with RKE2. Disabling the classes will bring another set of errors, although it the result is an OpenEBS that does work: + echo 'Installing helm_v3 chart' + helm_v3...

For those interested; I have K3S running on 4 StarFive Vision 2s using https://github.com/CARV-ICS-FORTH/kubernetes-riscv64. I have been able to port some more containers like the demo programs I use in...

Quoting Ingwie Phoenix ***@***.***>: Good day Ingwie, Kindly check https://github.com/CARV-ICS-FORTH/k3s/releases It is (was) a sponsored project. I am working with it for 3 months now, getting it working on Starfive...

Some more logs: [ 14.911231] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state [ 14.911239] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state [ 14.911288] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode. [ 14.911300]...

pascal@rock5bp-n01:~$ sudo dmesg | grep mmc [ 14.911231] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state [ 14.911239] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state [ 14.911288] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address...

@hanvinke You are right. The EMMC component is unsoldered on the board; which is probably the hardware equivalent of 'vapourware'. I actually bought 3 of these for the onboard EMMC...