CravenCode

Since Docker CE doesn’t support Kubernetes out of the box (like Docker for Windows/Mac) it’s up to us to figure out how to run it for local development. Using Minikube with KVM we can fairly painlessly get our environment running.

The Docker documentation for installing Docker CE under Ubuntu is really fantastic. This guide aims to provide a very opinionated step-by-step setup to give most developers a straightforward installation for local dev work.

When running Budgie (under Solus and Ubuntu Budgie) I found that I am not able to right click certain applications and select the “Pin to panel” option.

After recently installing Ubuntu Budgie, I noticed some applications installed via Snap sources were missing their application icons in the Budgie panel. While annoying, the fix is fairly straight-forward to implement once you know how.

Setting up Minikube required a little bit of trial and error on my part under Solus when trying to use the KVM2 driver. This guide provides repeatable instructions to successfully install Minikube with KVM.

While you won’t get a package file from Docker directly, the Solus Project’s eopkg command makes setting up Docker easy enough.

There are a couple aspects of Node.js that make using Docker for development somewhat difficult. The primary difficulties come from dependency differences based on environment and a long running server process during development.

When using Docker for development, it’s often necessary to bind mount directories from your host into your container. However, you’ll run into problems if your image contains files your host doesn’t (such as a node_modules directory). When that happens, you’ll need to get the files from your image into your host before you start your container with the mount.

At work we’re using Kubernetes with Docker for Mac on our local development environments—which has been amazing. However, devs often end up with dangling non-Kubernetes containers hanging around (from terminals being accidentally closed or VS Code reloads) keeping expensive Docker bind mounts around. This is a command I chained together to cleanup these extra containers without disturbing those in the Kubernetes deployment.

If you’ve ever ran commands on the command line that contain secure or sensitive information you certainly don’t want those commands recorded in your history.