Follow

Uninformed brief thoughts on Linux, container technology, Docker/Podman/Kubernetes/etc 

…I'm sure this will bring advantages down the road. The focus on namespacing, isolation, and declaring dependencies is great, especially in a world where not every package treats your system nicely.

That said, I'm not keen on how some projects distribute full-fat images.

And the transition curve is… fun.

Yes, I realize I'm making it harder on myself adapting a docker-compose.yml file into 's format, but I really don't want to run a giant root daemon ().

So far, I've gotten a container cluster. Just… need to make it very less kludgy, and integrate with configuration management.

Favorite snark:
youtu.be/HlAXp0-M6SY?t=374 "Kubernetes for Sysadmins – Kelsey Hightower at PuppetConf 2016"

All right, so here I'm saying from Ruby 2.3… That's probably gonna bring in an entire operating system.
Does anyone know why we bring in like an Ubuntu or Red Hat [OS] in these container images? Because most people don't know what the dependencies are; it's a shotgun approach.
Just take the whole OS and just shove it into the container, guaranteed I'm going to have my dependencies in there somewhere. And if not, just yum install the entire Internet and you're going to get your dependency at some point.

Sign in to participate in the conversation
The Vulpine Club

The Vulpine Club is a friendly and welcoming community of foxes and their associates, friends, and fans! =^^=