Cgroups. Using container technologies as a PaaS provider
summary
Claims running a PaaS without Docker or Kubernetes using Linux cgroups and POSIX features, backed by 15 years production at AlwaysData. Describes an orchestrator that writes pid numbers to cgroup.procs and edits files like memory.max to enforce caps, uses PAM-based ssh attachment to place sessions into per-user cgroups, creates private IPs and iptables rules, and says the system is simpler than container images and works in production.
AI-written summary · about
chapters (8)
- 0:00Cgroups and container isolation
- 7:41Microservices necessity
- 9:27Containers vs Linux isolation
- 12:56Alwaysdata’s cgroups cloud
- 17:34Automating cgroups orchestrator
- 20:50Namespaces and cgroups features
- 21:11POSIX and cgroups choice
- 22:34Cgroups and WebAssembly future
related talks
18mUser Space in Cloud Platforms
01h 01mYou have a container image: Now what?
23mOrchestration and CI/CD
44mThe Containerization of the Operating System: Exploring Bootc and the Future of Linux Deployment
19mRunD: A Lightweight Secure Container Runtime for High-density Deployment...
05mContainerization Beyond CPUs – A Kubernetes-based Serverless Pl...
44mDocker & Puppet: how to cross them and whether you need it
32mWhy you´re not ready for Containers in Production!