We are formalizing our container infrastructure as follows:
The Node role will continue to provide /usr/sbin/qemu-system-x86_64 for VM's
The Node role will additionally provide docker for long-running singleton containers, like TAK and Rancher, that are less tolerant of aarch64 in the Pi 4's
A Geth role will be created -- Geth will be k3s worker nodes managed by a Rancher container on Node. Tolerant containers & CTFs can then be deployed into the Pi4/k3s cluster & managed from there.
We are formalizing our container infrastructure as follows:
* The Node role will continue to provide `/usr/sbin/qemu-system-x86_64` for VM's
* The Node role will additionally provide docker for long-running singleton containers, like TAK and Rancher, that are less tolerant of `aarch64` in the Pi 4's
* A Geth role will be created -- Geth will be k3s worker nodes managed by a Rancher container on Node. Tolerant containers & CTFs can then be deployed into the Pi4/k3s cluster & managed from there.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We are formalizing our container infrastructure as follows:
/usr/sbin/qemu-system-x86_64for VM'saarch64in the Pi 4'sPull request closed