Isolating Containers with ZFS and Linux Namespaces(klarasystems.com) Containers provide an efficient way to isolate workloads, but managing storage and resource separation can be challenging. This article explores how ZFS and Linux namespaces work together to optimize containerized environments, ensuring storage flexibility, workload isolation, and enhanced control. Learn how to leverage ZFS datasets and Linux namespaces for multi-tenant architectures while maintaining performance and security.
Implementing a rootless container manager from scratch [video](fosdem.org) An introduction on the basic concepts underpinning a container manager: understanding what OCI images are, how they’re structured, and how to use them as rootfs. From there, we’ll dive into the core Linux primitives that make rootless containers possible: namespaces for isolation, UID/GID mappings and dropping privileges.
Any experience selling AMIs on AWS Marketplace?(ycombinator.com) AWS Marketplace allows AWS users to buy AMIs, containers, among other things (SaaS, consulting, etc). Does anyone here have experience selling goods (AMIs or containers)? Not interested in SaaS / service.
Deploying Containers on NixOS: A Guide(bkiran.com) Managing infrastructure on your own machine can be cumbersome and scary. Much of the rhetoric out there would have you believe that it’s not possible or very dangerous to run and manage your own server. There have been some great advances with tools like containers(Docker and Podman) and NixOS that makes this easier than ever.
Docker and OCI Hardening Guide(wonderfall.dev) Containers aren’t that new fancy thing anymore, but they were a big deal. And they still are. They are a concrete solution to the following problem:
272 points by twelvenmonkeys 98 days ago | 82 comments
SST: Container Support(sst.dev) Historically, SST has primarily supported deploying serverless applications. But over the last month we’ve slowly expanded native support for containers on AWS.
Flox, a better alternative to Dev Containers(medium.com) On paper, Dev Containers are great to define and share development environments easily. Actually using them is not that great: lack of reproducibility, integrating host files in containers, difference in implementations between various tools…
45 points by pierrebeucher 118 days ago | 17 comments
Fast Development with Zed and Dev Containers(medium.com) Ever found yourself saying “but it works on my machine” or spent hours setting up a development environment for a new team member? Dev Containers might just be the solution you’re looking for, and now you can use them with the blazingly fast Zed editor.
Ask HN: Kernel Containers (security like VMs, perf like LXC)(ycombinator.com) Frustrated by our own performance challenges with Kata Containers, we have developed a new hypervisor from scratch that can run each Docker container in isolation (i.e., no shared host kernel), and with native performance (i.e., no virtualization runtime overhead or cold starts).
Picking Glibc Versions at Runtime(blogsystem5.substack.com) In a recent work discussion, I came across an argument that didn’t sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn’t work and statically linking glibc wasn’t possible either.