This very much feels like disloyal competition. If you burn through your money in the hopes of sweeping out the competitors, and then you have to dial back on your competitor's practices, it's a dead giveaway you've done something fishy
Frank Drebin ramraids your front door, notes that you live with no front door, figures out you're quirky because nobody leaves the door open these days.
Toolbx now supports the use of the proprietary NVIDIA driver in containers without the need to recreate them or use special options. This is achieved through the use of NVIDIA Container Toolkit to generate a Container Device Interface specification on the host, which is then shared with the Toolbx container's entry point. The use of "nvidia-ctk" and "podman create" is not currently implemented due to root access requirements and the inability to update existing containers. The delay in enabling this support was due to the need for hardware access for testing, which was facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU.
Toolbx now supports proprietary NVIDIA driver in containers
NVIDIA Container Toolkit generates Container Device Interface specification on the host
Use of "nvidia-ctk" and "podman create" not implemented due to root access requirements and inability to update existing containers
Delay in enabling support was due to the need for hardware access for testing, facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU
I have an Intel Celeron laptop and an i7-4770k i7 desktop computer. Zypper is just too slow when you have many packages installed, but I require them for my work.
Regardless, a Celeron processor should be more than enough for downloading and updating packages. I'd rather not blame the hardware for a task as trivial as that.
Wrong place, wrong time