When MACOS changed the default shell from bash to zsh, I waited a bit, as I'd used bash for years and years, and was really familiar with it.

Post-clean install of Big Sur, I left my default shell as zsh.

Doing some reading, installed Oh My Zsh

Oh My Zsh is a delightful, open source, community-driven framework for …

The purpose was to have a Linux box act as a simple router.

Devices:

• Device1, configured with a 10.10.10.10 IP.
• Device2, which will be our router, configured with 2 interfaces: 10.10.10.1 and 192.168.1.245.
• Device3, which is my Internet-facing router, with an internal IP of 192.168.1.1

The router is going to be …

Horrible idea in a production box, but great idea for a single user lab system.

To accomplish this, we'll use the visudo command, which edits the /etc/sudoers file in a safe manner, aka, protect you from seriously messing up your system.

sudo visudo

At the bottom of that file, add (assuming your username is tom, …

Damn, that was a long, drawn out title….

Basics:

• As of this writing, I’m running TrueNAS 12.2

• While I really like TrueNAS, TrueNAS/FreeNAS doesn't support Docker containers.

• The TrueNAS team is working on TrueNAS SCALE, which is Linux-based, and support Docker containers, but it’s still in alpha.

• Once TrueNAS …

While testing out TrueNAS SCALE, I wanted to do some Docker-ing, and following best-practices, I tried to configure non-root access to the Docker daemon.

Fail !

I had added my username to the existing docker group:

sudo usermod -aG docker $USER

But I was still unable to use Docker, unless I was root:

docker ps
Got …

By default Docker needs to be run as the root user.

Not practical or advisable in a production, or shared system to be consistently logged in as root (think running with scissors).

Out of the box, attempting to run Docker as a non-root user gets this error:

whoami
tom

docker run hello-world
docker: Got permission …