Cracks in Containerized Development

linuxkit/linuxkit

A toolkit for building secure, portable and lean operating systems for containers

Home-Cooked Software and Barefoot Developers

The emerging golden age of home-cooked software, barefoot developers, and why the local-first community should help build it

How eBPF is shaping the future of Linux and platform engineering

When Docker burst onto the scene in 2013, Linux containers seemed like an overnight success. But the evolution to containers—and microservices and Kubernetes—was actually decades in the making, based on kernel primitives in the Linux operating system. Docker used these primitives, namely cgroups and namespaces, as building blocks to create a lightweight, easy-to-use software packaging format. Linux containers had been used by Google and others for many years, but Docker made them easily accessible to mainstream developers.

Are Package Registries Holding Open-Source Hostage?

This post examines Docker Hub pull limits, package registry lock-in, and why open source distribution needs better user-focused infrastructure.

A Docker Fork: Talk of a Split Is Now on the Table

Discussions about a split from Docker are now underway among several Docker ecosystem vendors and end users. Expressing frustration of

Container Escape Techniques: Breaking Out of the Digital Jail

How Attackers Break Free From Containerized Environments and What Defenders Need to Know

Aaron Boodman on Twitter / X

There is this tension in dev tooling right now: Lots of people want to self-host, and not depend on a service. Lots of people also want the vibes of open source - being part of an open development community, having the code, etc.But builders still need to make a living...— Aaron Boodman (@aboodman) January 23, 2024

Embrace Open Source, For the Good of Nerdmanity | Fortune

More businesses are willing to use open source software for key projects.

Ten FOSS Development Fallacies For User Facing Software

This is a list, inspired by the Five Geek Social Fallacies, of common patterns or behaviours that developers of free/open source software (FOSS) fall into when they try to develop software for users who are not technical, or for whom non-technical users would be the most obvious userbase. Hopefully writing these down (which frankly is cathartic more than anything) is helpful to some in recognising these thought patterns and avoiding them when developing software - I’ve got some of my own thoughts on this at the bottom.

The Missing Middle of Open Source

Why serious, maintainer-driven projects struggle to sustain themselves—and what it will take to fix it.

Composable, fast, and secure dev environments | Workshop | Ubuntu

Launch agent-ready, sandboxed development environments with a single command. Define them via simple YAML configs, share them to recreate on different machines.

WTF is a container? | TechCrunch

You can't go to a developer conference today and not hear about software containers: Docker, Kubernetes, Mesos and a bunch of other names with a nautical

Working in Public: The Making and Maintenance of Open S…

An inside look at modern open source software developer…