Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
docker_notes:vm-container [2024-06-01 Sat wk22 19:59] – [KVM versus Proxmox] baumkp | docker_notes:vm-container [2024-07-07 Sun wk27 11:21] (current) – [KVM versus Proxmox] baumkp | ||
---|---|---|---|
Line 2: | Line 2: | ||
======Docker Host ====== | ======Docker Host ====== | ||
=====KVM versus Proxmox===== | =====KVM versus Proxmox===== | ||
- | I originally started using Linux KVM based VM, with QEMU and Libvirt on Ubuntu bare metal, circa 2014, this before was I was aware that Proxmox existed. | + | I originally started using Linux KVM based VM, with QEMU and Libvirt on Ubuntu bare metal, circa 2014, this before was I was aware that Proxmox existed. |
Interestingly as I understand it Proxmox uses Debian and Linux KVM VM, however they also provide a lot of additional functionally, | Interestingly as I understand it Proxmox uses Debian and Linux KVM VM, however they also provide a lot of additional functionally, | ||
Line 10: | Line 10: | ||
I may try Proxmox in the future, there is currently no compelling reason for me to do so at this time. | I may try Proxmox in the future, there is currently no compelling reason for me to do so at this time. | ||
- | My current router has an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but still functions well as a sub gb/s router. | + | My current router has an Intel N3700 CPU, maximum 8GB ram, procured in 2016, which in 2024 is becoming slow to use, but still functions well as a sub gb/s router. |
- | My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 2.5Gb/s PCIe card. I have not been able to find a good replacement for this machine at this time. It was designed as a server, again an i5-1335U is in many ways superior, CPU cores and threads, CPU and memory speed and bandwidth, however memory is not ECC and memory is limited to 64GB, neither of which is probably a problem for me, as I am currently only using 32GB. Power consumption is similar. The biggest problem is that I have not been able to date find an i5-1335U motherboard with 4+ SATA ports and PCIE expansion slot, most are laptop boards, router boards or industrial embedded type boards that do not have the functionality that I am after. | + | My main home server is based upon an Intel Atom C3750 server, this is still currently adequately meeting my needs. I have upgraded with a 2.5Gb/s PCIe card. |
Line 18: | Line 18: | ||
I use Linux KVM with libvirt, virsh and qemu. | I use Linux KVM with libvirt, virsh and qemu. | ||
* Install standard Debian files. See [[https:// | * Install standard Debian files. See [[https:// | ||
- | * I simply do not need a GUI. Where convenient I may separately install a GUI that can be accessed via VNC. | + | * I simply do not normally |
* Add user to libvirt and libvirt-qemu, | * Add user to libvirt and libvirt-qemu, | ||
* If you are ssh' | * If you are ssh' | ||
Line 28: | Line 28: | ||
* Set static ip address and a bridge network (this varies on the install type) | * Set static ip address and a bridge network (this varies on the install type) | ||
* For networkd: | * For networkd: | ||
- | * '' | + | * '' |
- | * ''/ | + | *The KVM virtual machine does not necessarily need a bridge network, but does usually need a static IP address |
- | + | *Docker does not specifically require a HOST with bridge | |
- | # The loopback network interface | + | * ''/ |
+ | ++++source / | ||
+ | <code bash># The loopback network interface | ||
auto lo | auto lo | ||
iface lo inet loopback | iface lo inet loopback | ||
Line 44: | Line 46: | ||
address 192.168.1.2/ | address 192.168.1.2/ | ||
gateway 192.168.1.1 | gateway 192.168.1.1 | ||
- | # | + | |
bridge_stp off # disable Spanning Tree Protocol </ | bridge_stp off # disable Spanning Tree Protocol </ | ||
- | | + | ++++ |
====Reference==== | ====Reference==== | ||
*[[https:// | *[[https:// | ||
<- docker_notes: | <- docker_notes: |