Why does this feel like it’s a flat-earth slide? I haven’t looked at any flat-earth propaganda, but I strongly suspect that it looks a lot like this.
That said, I’ll stick with my VMs regardless. I like simplicity.
Nix has flakes;
nix runcan contain pretty much all of the needed dependencies. If that’s not enough, you can set up an entire container as a module.Are VMs really simpler? I’d say no.
I was so relieved to never need VM’s again after discovering Docker.
The absurd waste of resources VMs bring… LXC and Docker a godsend in that regard.
I would vote for docker as well. The last time I had to inherit a system that ran on virtual machines, it was quite a pain to figure out how the software was installed, what was where in the file system, and where all the configuration was coming from. Replicating that setup took months of preparation.
By contrast, with Docker, all your setup is documented. The commands that were used to install our software into the virtual machines and were long gone are present right there in the Docker file. And building the code? An even bigger win for Docker. In the VM project, the build environment for the C++ portion of our codebase was configured by about a dozen environment variables, none of which were documented. If it were built in Docker, all the necessary environment variables would have been right there in the build environment. Not to mention the build commands themselves would be there too, whereas with VMs, we would often have developers build locally and then copy it into the VM, which was terrible for reproducibility and onboarding new developers.
That said, this all comes down to execution - a well-managed VM system can easily be much better than a poorly managed Docker system. But in general, I feel that Docker tends to be easier to work with than a VM. While Docker is far from flawless, there are a lot more things that can make life harder with VMs, at least from my experience.
Reject whale, join the kubernetes cluster.
We have fully automated gay space crashloopbackoff!
Absolutely the best kind of space crashloopbackoff.
For real though, containerization isn’t the only way to separate applications from each other but totally fine, it’s the “It works on my machine, so here’s my machine” mentality that doesn’t fill me with confidence. I’ve seen too much barely-working jank in containers that probably only get updated when a new version of the containerized application itself is released.
Nix user arrives to the room.
Can you elaborate?
I like containers. But they do have a habit of nurturing cludgy temporary hacks into permanent infrastructure, by sweeping all the ugly bits under the big whale-shaped rug.
Containers are a great way run applications.
Docker is a piece of garbage by a company way too far down the enshittification slide.
I wish I understood this because it seems funny
Moral of the story: never make breaking changes. Always backwards compatible, always.
It’s worked for Windows?
It’s not that funny.
Docker is like a virtual machine, but you only run one specific program in it. About exactly what the meme describes.
You ain’t missing much
I don’t like containerisation because it leads to bullshit like atomic distros. I don’t want a spicy Android.
Steam OS has some cool elements like the menu, the in-game side panels and the game mode/desktop dichotomy, but incremental rolling release is utterly deranged from my POV as an Arch user (btw).
I’m currently trying Fedora Kinoite and from the get go the hassle of getting a proper Firefox+codecs to watch online videos feels like a major step back.
Then you have the issue of installing software in flatpack (is: vscode, texmaker) that are either not fully working of need to have their access tweaked. Atomic distros appeal is to “just work” it doesn’t seem like it does.
If stability is deranged then yes.
As someone having used Arch, stuff does break at times and Valve can’t link a Wiki link with the fixes
Meh, this one is weak.
Weak one. Let’s ideate on a better version
STOP DOING DOCKER
-
Virtualization was supposed to reduce the overhead, not create entire DevOps departments.
-
Years of containerization yet no real use over
make clean; make build -
Wanted to deploy your app in the “cloud” anyways for a laugh? we had a tool for it, it’s called
rsync -
Let’s run a virtual container in
--privilegedmode, so we can manage system resources from it – Statements dreamt up by utterly Deranged
Look at what tech interviews have been demanding your Respect for all these years. (These are real documentation examples for how a simple virtualization supposedly works)
–
Hello, I would like to put 20 Terabytes of “images” into my
/var/lib/, please!They played us for absolute fools!
A good example of a similar meme: https://i.redd.it/uew0stv0mff61.jpg
-
BSD Jails have entered the chat …
Kubernetes: I will ruin your fucking life
I’ve recently spent a fair amount of time trying to peel my blog away from my existing framework due to how much I hated using docker to just build a website, it doesn’t need to be this heavyweight.
This meme but unironically
