The assessments are here - Revision history

Lynn at 01:15, 4 September 2026

2026-09-04T01:15:51Z

← Older revision		Revision as of 18:15, 3 September 2026
Line 1:		Line 1:
	The software landscape is vast. It is a little like being in a candy store the size of a Walmart. With hypervisors like Proxmox and TrueNAS it is rediculously easy to sping up virtual machines or launch software with docker. What used to take hours installing an OS and configuring a physical resource only takes minutes. Installing software used to be its own hurdle. Getting it to work on you specific combination of hardware and OS could literally take days.		The software landscape is vast. It is a little like being in a candy store the size of a Walmart. With hypervisors like Proxmox and TrueNAS it is rediculously easy to sping up virtual machines or launch software with docker. What used to take hours installing an OS and configuring a physical resource only takes minutes. Installing software used to be its own hurdle. Getting it to work on you specific combination of hardware and OS could literally take days.

	=The tools ~~That~~ I use, or have used=		=The tools that I use, or have used=
	In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works. These are listed roughly in order of use.		In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works. These are listed roughly in order of use.
	==Hypervisors==		==Hypervisors==

Lynn: /* The tools That I use, or have used */

2026-08-21T21:57:09Z

The tools That I use, or have used

← Older revision		Revision as of 14:57, 21 August 2026
Line 2:		Line 2:

	=The tools That I use, or have used=		=The tools That I use, or have used=
	In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works.		In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works. These are listed roughly in order of use.
	==Hypervisors==		==Hypervisors==
	For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes, it can be done but I personally think that it is crazy.		For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes, it can be done but I personally think that it is crazy.

Lynn: /* VMWare */

2026-08-21T21:56:25Z

VMWare

← Older revision		Revision as of 14:56, 21 August 2026
Line 9:		Line 9:
	Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It passed through EMC, Dell and then to Broadcomm. Broadcomm eliminated the perpetual licensing, and the cost of ownership went way up.		Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It passed through EMC, Dell and then to Broadcomm. Broadcomm eliminated the perpetual licensing, and the cost of ownership went way up.

	It was possible to download the product and get a limited use key. After yet another acquisition by venture capital firm KKR, the VMWare Workstation Pro and VMWare Player shifted to a free for personal use status, but these ae really intended for an individual developer's desktop rather than a server ~~application~~.		It was possible to download the product and get a limited use key. After yet another acquisition by venture capital firm KKR, the VMWare Workstation Pro and VMWare Player shifted to a free for personal use status, but these ae really intended for an individual developer's desktop rather than a server implementation.

	===Hyper-V===		===Hyper-V===
	===VirtualBox===		===VirtualBox===

Lynn: /* Hypervisors */

2026-08-21T21:53:57Z

Hypervisors

← Older revision		Revision as of 14:53, 21 August 2026
Line 5:		Line 5:
	==Hypervisors==		==Hypervisors==
	For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes, it can be done but I personally think that it is crazy.		For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes, it can be done but I personally think that it is crazy.


	===VMWare===		===VMWare===

Lynn: /* Hypervisors */

2026-08-21T21:53:39Z

Hypervisors

← Older revision		Revision as of 14:53, 21 August 2026
Line 4:		Line 4:
	In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works.		In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works.
	==Hypervisors==		==Hypervisors==
	For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes it can be done but I personally think that it is crazy.		For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes, it can be done but I personally think that it is crazy.
	~~===Proxmox===~~
	~~===TrueNAS===~~
	~~===Hyper-V===~~
	===VMWare===		===VMWare===
	Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It passed through EMC, Dell and then to Broadcomm. Broadcomm eliminated the perpetual licensing, and the cost of ownership went way up.		Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It passed through EMC, Dell and then to Broadcomm. Broadcomm eliminated the perpetual licensing, and the cost of ownership went way up.

	It was possible to download the product and get a limited use key. After yet another acquisition by venture capital firm KKR, the VMWare Workstation Pro and VMWare Player shifted to a free for personal use status, but these ae really intended for an individual developer's desktop rather than a server application.		It was possible to download the product and get a limited use key. After yet another acquisition by venture capital firm KKR, the VMWare Workstation Pro and VMWare Player shifted to a free for personal use status, but these ae really intended for an individual developer's desktop rather than a server application.
			===Hyper-V===
	===VirtualBox===		===VirtualBox===
	This was the first virtualization product that I used. It runs on a number of architectures as an application. It was developed by Sun Computer Systems and moved to Oracle when Sun was acquired.		This was the first virtualization product that I used. It runs on a number of architectures as an application. It was developed by Sun Computer Systems and moved to Oracle when Sun was acquired.
			===Proxmox===
			===TrueNAS===

	It is a nice tool for testing on your desktop.		It is a nice tool for testing on your desktop.

Lynn: /* The tools That I use, or have used */

2026-08-21T21:51:06Z

The tools That I use, or have used

← Older revision		Revision as of 14:51, 21 August 2026
Line 2:		Line 2:

	=The tools That I use, or have used=		=The tools That I use, or have used=
			In my opinion, it makes no sense to run a hypervisor tool like VirtualBox or VMWare Workstations since it makes more sense to run docker natively rather than going to the complexity of a layer of abstraction. I also think that attempting to try to do this on a desktop is a little crazy as well. At the same time, if it was you have to test with; if it works, it works.
	==Hypervisors==		==Hypervisors==
	For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes it can be done but I personally think that it is crazy.		For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes it can be done but I personally think that it is crazy.
Line 8:		Line 9:
	===Hyper-V===		===Hyper-V===
	===VMWare===		===VMWare===
	Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It was possible to download the product and get a limited use key. ~~You can still get freeware copies of~~ VMWare Workstation Pro and VMWare Player for ~~free~~, but these ae really intended for an individual developer's desktop rather than a server application.		Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It passed through EMC, Dell and then to Broadcomm. Broadcomm eliminated the perpetual licensing, and the cost of ownership went way up.

			It was possible to download the product and get a limited use key. After yet another acquisition by venture capital firm KKR, the VMWare Workstation Pro and VMWare Player shifted to a free for personal use status, but these ae really intended for an individual developer's desktop rather than a server application.
	===VirtualBox===		===VirtualBox===
	This was the first virtualization product that I used. It runs on a number of architectures as an application. It was developed by Sun Computer Systems and moved to Oracle when Sun was acquired.		This was the first virtualization product that I used. It runs on a number of architectures as an application. It was developed by Sun Computer Systems and moved to Oracle when Sun was acquired.

Lynn: /* Hypervisors */

2026-08-21T21:36:13Z

Hypervisors

← Older revision		Revision as of 14:36, 21 August 2026
Line 8:		Line 8:
	===Hyper-V===		===Hyper-V===
	===VMWare===		===VMWare===
	Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It was possible to download the product and get a limited use key. You can still get freeware copies of VMWare Workstation Pro and ~~VMWARE player~~		Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It was possible to download the product and get a limited use key. You can still get freeware copies of VMWare Workstation Pro and VMWare Player for free, but these ae really intended for an individual developer's desktop rather than a server application.
			===VirtualBox===
			This was the first virtualization product that I used. It runs on a number of architectures as an application. It was developed by Sun Computer Systems and moved to Oracle when Sun was acquired.

			It is a nice tool for testing on your desktop.

	==Foundations==		==Foundations==

Lynn: /* Hyper-V */

2026-08-21T21:30:47Z

Hyper-V

← Older revision		Revision as of 14:30, 21 August 2026
Line 7:		Line 7:
	===TrueNAS===		===TrueNAS===
	===Hyper-V===		===Hyper-V===
			===VMWare===
			Stay away, far, far away and it is still too close. They were the Gold Standard and about the only virtualization tool on the block. A decade or so, ago VMWare treated noncommercial users pretty well. It was possible to download the product and get a limited use key. You can still get freeware copies of VMWare Workstation Pro and VMWARE player

	==Foundations==		==Foundations==
	===Docker===		===Docker===

Lynn: /* The tools That I use, or have used */

2026-08-21T21:01:08Z

The tools That I use, or have used

← Older revision		Revision as of 14:01, 21 August 2026
Line 7:		Line 7:
	===TrueNAS===		===TrueNAS===
	===Hyper-V===		===Hyper-V===
			==Foundations==
			===Docker===
			====Docker Compose====
			====Dockerge====
			====Dockhand====
			===VPN===
			====Private Internet Access====
			====Nord====
			==Docker Stacks==

	=YAMS=		=YAMS=
	[https://gitlab.com/rogs/yams YAMS on Github]		[https://gitlab.com/rogs/yams YAMS on Github]

Lynn: Created page with "The software landscape is vast. It is a little like being in a candy store the size of a Walmart. With hypervisors like Proxmox and TrueNAS it is rediculously easy to sping up virtual machines or launch software with docker. What used to take hours installing an OS and configuring a physical resource only takes minutes. Installing software used to be its own hurdle. Getting it to work on you specific combination of hardware and OS could literally take days. =The tools..."

2026-08-21T02:00:27Z

Created page with "The software landscape is vast. It is a little like being in a candy store the size of a Walmart. With hypervisors like Proxmox and TrueNAS it is rediculously easy to sping up virtual machines or launch software with docker. What used to take hours installing an OS and configuring a physical resource only takes minutes. Installing software used to be its own hurdle. Getting it to work on you specific combination of hardware and OS could literally take days. =The tools..."

New page

The software landscape is vast. It is a little like being in a candy store the size of a Walmart. With hypervisors like Proxmox and TrueNAS it is rediculously easy to sping up virtual machines or launch software with docker. What used to take hours installing an OS and configuring a physical resource only takes minutes. Installing software used to be its own hurdle. Getting it to work on you specific combination of hardware and OS could literally take days.

=The tools That I use, or have used=
==Hypervisors==
For the most part these tools are bare metal installs. Let's not get into the crazy case where a hypervisor is installed on a hypervisor. Yes it can be done but I personally think that it is crazy.
===Proxmox===
===TrueNAS===
===Hyper-V===

=YAMS=
[https://gitlab.com/rogs/yams YAMS on Github]