To make your guest VM work regardless of the LAN configuration, you will need to attach a host only adapter as your first adapter, and then a NAT adapter as your second adapter for the guest.ġ. Of course, if you are just running this on your own home network, you could just reserve an IP address in your router for the VM, but that will not work when you are visiting a friend, at work, or at the library. Without a static IP for your VM, you risk having to update your host file occasionally, which is not very practical.Įach local domain should point to the VM IP address of the Host-only adapter.

After installing Ubuntu, you should install SSH, and then run VirtualBox in headless mode. I am not going through the installation process in this article, so I assume you already know how to setup and install Ubuntu.Ģ. Since I had no use for a GUI in the GUEST system, I decided to install Ubuntu Server. Doing this allowed me to run the latest version of my operating system, while my development environment was running the LTS version of Ubuntu Server.ġ. I carefully created a setup that would allow me to still do my coding from the host system, while the servers and all the code was running in the containerized guest. It appears that this problem has since been fixed in the official repositories.Įven though the problem appears to have been fixed, I have now realized that I can not safely have my development environment coupled with my personal system - to avoid future incidents like this, I would have to install my test-servers in a containerized environment, like VirtualBox - surprisingly this was not very hard to do.ĭoing this also allows me to run a different OS or Linux distribution for my main OS for server stuff you might prefer Ubuntu, but for your main OS you might prefer to use Arch Linux, KDE Neon or even Windows.

Virtualbox static ip ubuntu