Lately, I have worked for Red Hat, the largest open source software company in the world. Through a variety of roles in my career, I have played key roles in building, maintaining, marketing, and selling open source software products and services.
In years past I was a social media start-up veteran, e-commerce old timer, and weathered government research technologist. This has led to experience in a variety of companies and organizations ranging from a seven person start-up to a 8,000 person technology company. This has culminated in a unique perspective on open source software development, delivery, and maintenance.
Updated 06/02/2020 Understanding Container Images To fully understand how to compare container base images, we must understand the bits inside of them. There are two major parts of an operating system – the kernel and the user space. The kernel is a special program executed directly on the hardware or virtual machine – it
Background For years, I floundered around with moving my own blog, ticket system and wiki into containers. Literally, ticket #627: Migrate Crunchtools to Containers has been open in Request Tracker since March 11th, 2017. It’s embarrassing to admit given how deeply I have been involved with containers at Red Hat. Since the early days of
Let’s dig into these three concepts a bit deeper: Portability Since the OCI standard governs the images specification, a container image can be created with Podman, pushed to almost any container registry, shared with the world, and consumed by almost any container engine including Docker, RKT, CRI-O, containerd and, of course, other Podman instances. Standardizing
Perhaps you’ve been charged with developing a container-based application infrastructure? If so, you most likely understand the value that containers can provide to your developers, architects, and operations team. In fact, you’ve likely been reading up on containers and are excited about exploring the technology in more detail. However, before diving head-first into a discussion