Docker Hosts
Introduction
this page will be concerned with the actual hosts more general information about Docker can be found here. We need to have some Virtual Machines to host the containers so that processing is reasonably separated and constrained with no one container gaining all of the CPU or GPU cycles of the entire Proxmox host. Another, possibly more important, consideration is that if the OS of Pear is upgraded we don't want to break a load of containers. The last point for VMs for containers is that Nvidia are fairly well known for breaking there drivers sometimes while they are being upgraded. So better to leave the GPU driver update until other people have tested it and do any Proxmox updates as a separate job.
GPU Host Quince
We are using Quince 192.168.100.75/24 as the host for GPU Passthrough and as a consequence it will have Jellyfin and Ollama docker containers.
Quince Specification
To store the OS we have a 150gb drive allocated from the SSD Rpool and to keep all of the media files we have a 3TB hard drive allocated from Pearpool. As a temporary measure the media HD from Walnut has also been added to enable the media files to be copied to the new HD, it was impractical to keep the walnut HD on quince as it is NTFS and quince is Linux so while it would work it is not the preferred.
- Hostname is Quince
- IP Address is 192.168.100.75/24
- RAM is 32gb
- Processor is type Host and has 1 socket with 10 cores
- Bios is OVMF (UEFI)
- Machine type is q35
- OS Storage is 150gb allocated from Rpool
- Media storage is 3tb allocated from Pearpool
- NIC is on production VLAN
- Display is set to default
- PCI device is 0000:07:00 (the Nvidia 5060ti 16gb GPU)
