Jacob Blain Christen

> ``` > pi@k4s-1:~ $ chmod +x k3c-linux-arm > pi@k4s-1:~ $ ./k3c-linux-arm > Illegal instruction > pi@k4s-1:~ $ uname -a > Linux k4s-1 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41...

@sureshsankaran yes, we want to support this. The first cut of this will likely copy import/export from `ctr` but I think the tarball format is slightly incompatible with Docker.

Hey, since no one asked, here is my opinion: https://github.com/harvester/harvester/issues/2245#issuecomment-1166152229 Or in other words, fix fleet (or the rancher code?) by one of the following: - correct the serialization hints/hacks...

SRV records from the docker daemon's DNS would allow one to build such an external router. So would a routing policy framework/plugin, one imagines.

I was assuming Layer 7 as that is what I am used to building (and would require externally accessible ports) but if IPVS supports stickiness (which I would be surprised...

@kelseyhightower I agree the additional API endpoints on top of DNS SRV records is a real nice to have (a la Consul). As for services exposing multiple ports, I am...

@Drtuna private registries via `/etc/rancher/k3s/registries.yaml` was not added until 1.0 (see https://github.com/rancher/k3s/issues/99). Have you tried using an up-to-date version of k3s?

Related to https://github.com/rancher/kim/issues/74 I think. If this is indeed the same behavior (assuming you are using the containerd worker), workarounds are: - adjust build export/output params with `unpack=true` (or `type=docker`)...

> We could use a lightweight version of this where we can at least specify a delay between node upgrades so that we avoid having multiple nodes rebooting before a...

@tianon could this be related to statically compiled CGO for arm with version of golang prior to 1.16? (there were a number of compiler/toolchain enhancements that seem to have addressed...