Editing Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software (section)

== 2. Time-Efficient Migration from Physical to Virtual ==

Taking a physical server and turning it into a virtual machine takes no effort.

# Pull drive out of physical server.
# Run <code>ddrescue -f -d -r 3 /dev/sdb phonesystem.iso</code>
# Open virtual machine manager
# Enter a few commands in terminal to create a bridge network interface so the virtual machines work; once done, I never have to do this again for any other virtual machine.
# Import the <code>phonesystem.iso</code> file as a virtual machine.
# Mess with BIOS/UEFI settings if necessary in virtual machine manager to get it to work.
# Assign the virtual machine the amount of CPU cores/RAM I think it should have based on what it is doing.
# Run it.
# Be happy.

It only takes a few seconds to type the commands &amp; click the icons necessary in virtual machine manager. Compare that to re-architecting the entire system for Docker: it would have taken way more effort, downtime, etc. for an improvement in performance I will never notice as a person who has a few users for my server.

Some of these servers were running years before Docker was a thing, &amp; fixing what wasn’t broken made no sense. Virtual machines offered a way to keep my systems running as they were once the hardware died &amp; have them set to back up with no extra work on my part.

Over the years, I changed to using programs that were in docker exclusively. I went from a normal nextcloud deployment where I manually installed everything from scratch(including dependencies) to immich for images which was all docker. I went from self-managed email where the individual components(mailcot, dovecow, mysql, rspamd, etc.) were all installed from scratch to mailcow. Along the way, I just installed the dockerized version of the program on the virtual machine that was assigned to that “group” of services

<span id="certain-programs-arent-built-for-docker"></span>