There seems to be some confusion around sandboxing containers as of late, mostly because of the recent launch of gvisor… There is a large amount of ignorance towards the existing defaults to make containers secure. Which is crazy since I have written many blog posts on it and given many talks on the subject.
Jessie has been doing the yeoman’s work of Linux kernel isolation and making containers secure for awhile now, but much of that work has been overlooked or disregarded by others in the community. I’m on the outside looking in at this situation, so it’s tough to call exactly what’s going on, but according to Jessie:
When you work at a large organization you are surrounded by an echo chamber. So if everyone in the org is saying “containers are not secure,” you are bound to believe it and not research actual facts.
That doesn’t mean Jessie thinks containers are secure (click through to read her take on that). There’s a lot to dig in to here and think about. I’ll pull out one last point:
I am not trying to throw shade at gvisor but merely clear up some FUD in the world of open source marketing. I truly believe that people choosing projects to use should research into them and not just choose something shiny that came out of Big Corp.
Now that’s a sentiment I can get behind! Oh, and listen to this related episode of The Changelog if you haven’t yet. It’s a must-listen for all developers.