Skip to content
0:00 / 0:00

#smartos#illumos#solariszones

Run containers on bare metal already!

Bryan Cantrill

9.1K subscribers • 4 videos on Hallway

YouTube
  • Recommended by 4 people: 3 on Hacker News and 1 on Lobsters.
  • A classic. People kept recommending it from 2015 to 2025.
  • Presented by Bryan Cantrill, CTO of Joyent
  • May be out of date. Uploaded 10 years ago, in an area where tools change fast.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

40K views10 years ago4 recommendations

Systems programmingCloud and DevOpsDocker and containersOperating systemsLinux

Bryan Cantrill argues against layering containers on top of virtual machines and explains how SmartOS runs Linux workloads via syscall emulation.

My presentation at Velocity NYC 2015.

Why it's here

4 people recommend this

What people say. Recommended for its energetic and informative critique of virtualization overhead and its explanation of bare-metal container architectures.

kbensonon Hacker News • Recommends

On “My VM is lighter and safer than your container”

SmartOS's LX branded zones seem kind of cool to me, and may hit an interest point for you. Basically, SmartOS is an OpenSolaris variant where they use Solaris Zones for docker images, but they've implemented a Linux syscall table API so you can create Linux "compatible" containers from a Solaris kernel (and also full access to ZFS, etc). You can see a talk here1 where Bryan Cantrill goes over the reasons you might want to use containers, SmartOS and how LX branded zones. Warning though, he's an extremely engaging speaker, so not only are you likely to watch all of that 40 minute talk, but you might feel like binging on some other talks of his, so here you go.2 1: link to this video 2: link

latteraon Lobsters • Recommends

Run containers on bare metal already!

dpetersonon Hacker News • Recommends

On “EC2 Dedicated Hosts”

I have run containers on bare metal and in Amazon. Performance can be noticeably slower in Amazon on machines with similar specifications. A detailed explanation why is in this informative video by Bryan Cantrill link to this video . It is a talk about how layering containers on top of virtual machines is a recipe for poor performance and wasted resource utilization. He equates it to developers “being given fire, then proceeding to put the fire out.”

cpetersoon Hacker News • Recommends

On “What is a 'unikernel'?”

Unikernels : hypervisor :: processes : traditional operating system Joyent CTO Bryan Cantrill gave a great talk at Velocity NYC 2015 about the history of containers (going back to March 18, 1982 when Bill Joy added the chroot system call) and the problems of running containers on operating systems in VMs on hypervisors: "Stop killing kittens and melthing the ice caps: Run containers on bare metal already!" link to this video

kbensonon Hacker News • Recommends

On “Immutable Software Deploys Using ZFS Jails on FreeBSD”

…would be no guarantee that the underlying software wouldn't exhibit bugs or weird behavior from small behavior differences in the platform when emulating something else. Why open yourself up to the headache when you can just run Linux with containers or build what you want on FreeBSD with jails and their own native containerization primitives. 1: link to this video…

kbensonon Hacker News • Mentions

On “What is a 'unikernel'?”

From a recent post, here's a talk1 about containers where they use SmartOS (Solaris/IllumOS derivative) to containerize Linux by just implementing the syscall table. The future of hosting legacy apps might be providing legacy interfaces on modern OS's (IMO). 1: link to this video

bradgessleron Hacker News • Mentions

On “Challenges of Deployment to ECS”

The biggest missed opportunity of ECS that AWS missed was completely hiding the complexity and concerns of managing EC2 instances. If you use ECS you have to deal with the complexity of both and manage those resources. The dream being sold by the container industry is that you don't really care about the machines you're containers are running on. ElasticBeanstalk gets this right because they hide that concern. ECS is akin to selling git on top of SVN. It doesn't really make sense. Bryan Cantrill gave a talk about the craziness of running containers on VMs at link to this video .

Annataron Hacker News • Mentions

On “Why we use the Linux kernel's TCP stack”

> What most people call "containers" was always about virtualization (ie isolation), and the isolation primitive in the Linux kernel is namespaces. There is no isolation with cgroups in Linux, that is the crux of the matter: link to this video since containers in Solaris existed before cgroups and before the entire Linux hype, and you specifically adress my "misunderstanding" (of hype), you compel me to correct on terminology: containers are resource constraints, while technology like LXC and OpenVZ provide the lightweight virtualization and isolation , a very important distinction (full virtualization is achieved via XEN and KVM on GNU/Linux). Conceptually, as a resource constraint, containers are in…

drbawbon Hacker News • Mentions

On “We Replaced Firecracker with QEMU”

The second I read "shared block cache" my brain went to containers. If you want data colocated on the same filesystem, then put it on the same filesystem. VMs suck, nobody spins up a whole fabricated IBM-compatible PC and gaslights their executable because they want to. 1 They do it because their OS (a) doesn't have containers, (b) doesn't provide strong enough isolation between containers, or (c) the host kernel can't run their workload. (Different ISA, different syscalls, different executable format, etc.) Anyone who has ever tried to run heavyweight VMs atop a snapshotting volume already knows the idea of "shared blocks" is a fantasy; as soon as you do one large update inside the guest…