mib

@wiegell did you find a fix?

> > @wiegell did you find a fix? > > I got it solved but i'm not even sure how. I think i ended up commenting again and just recompiled...

For future reference: it seems UID & GID 1000 are used (inherited from `docker.io/node` images).

Any updates on this? Is the crate still being maintained?

Hmm. Yeah I didn't get anything like that error when testing, but it also wasn't _super_ thorough. @Yanik39, could you provide some more details about your use-case?

I am also having this issue with Cilium on a freshly-made Scaleway-managed cluster. No configuration of the `linkerd-cni` being enabled and running on stable or edge work. Also tried installing...

There are a few similar things for other components. (I'm assuming not every component needs access to the old signing keys / the TLS certs / matrix key?) I'm struggling...

> I'll try that! > > Quick note: Xen claims `iommu=no-igfx` having an effect [points to a bug](https://xenbits.xen.org/docs/unstable/misc/xen-command-line.html), though they don't say weather it's a Xen-bug or dom0-driver-bug. Did that...

The closing PR (#207) doesn't really address all use cases for a binary cache, such as deploying to a host with a different system (i.e. deploying from `x86_64-linux` _to_ `aarch64-linux`)....

I've set up a cache at [deploy-rs.cachix.org](https://deploy-rs.cachix.org) ([repo](https://github.com/mibmo/deployrs-binary-cache)) and am working on populating it with CI (a.la [the previous one](https://github.com/cmacrae/deploy-rs-binary-builds)). I've currently got it building `x86_64-linux` and `aarch64-linux` (see [pins](https://app.cachix.org/cache/deploy-rs#pins)),...