linux - lesser daemon

09

Apr

Provisioning a Red Hat VirtualBox VM With Vagrant

In what I hope will be the last entry in the "Brent learns the basics of VM provisioning" series, I finally moved to using Hashicorp's Vagrant yesterday. I'm glad I took the time to mess around in VirtualBox itself first - I always like understanding what I'm working with before I move to abstractions - but Vagrant makes it significantly easier. Vagrant sets up SSH in your VM by default, which is a nice time-saver, and generally makes the process of automating VM setup quick and easy. Behold:

1) Install Vagrant & VirtualBox.

2) In your project folder, add the

Setting Up Port Forwarding on a VirtualBox RedHat VM With A NAT Network Adapter

OK, quickly discovered that I was less brilliant than I thought yesterday. It appears that for the functionality I wanted (both the ability to SSH into the VM and to port forward from my local machine to an application running on the VM) I need to use a NAT and not a bridge network.

I spent a while struggling with this and discovered that to assign your VM to the standard 10.0.2.* range and successfully connect to the internet, a NAT drive should be your first network adapter. I'd initially had a bridge network as Adapter 1 and

Setting Up SSH And Shared Folders in A RHEL VirtualBox VM

I discovered recently that RHEL has a free developer license, something that could have saved me a lot of trouble if I'd known it earlier. Since I do a lot of work in RHEL I've wanted to have a virtual environment that mimics it - I had been working in WSL, but I think having to work with VirtualBox VM does a better job of replicating the experience of working on it in production.

You'll need to get a RHEL Developer License to download the necessary ISO image. You can pretty much roll with the default settings while creating the

Checking Disk Space On An Ubuntu Server

du -cha --max-depth=1 / | grep -E "M|G"

From this StackOverflow answer - ncdu is also a good tool for this, allegedly, but its output didn't really seem to have any correlation to the actual folders on my server. I feel like I have to do this once a year because of storage issues and always forget, so hopefully this serves as a reminder going forward. Turns out snap is the culprit, as per usual. In a fit of pique I uninstalled snap and all of its files, and lo and behold I'm able to finally update Ghost!