Reject whale, join the kubernetes cluster.
We have fully automated gay space crashloopbackoff!
Absolutely the best kind of space crashloopbackoff.
Reject kubernetes, join the Juju cluster.
We have "save your wallet hundreds of thousands by not automatically spinning up a crapton of resources if your app does an oopsie"! And we have "simply run on any public cloud or in your own datacenter with MAAS or locally with LXD"!
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?
Nix can build you a bit-to-bit exact environment for your app. It is a superior environment, but is hard to use in the beginning and users can feel snobby sometimes. It is awesome, but YMMV.
How do you separate Nix programs from the rest of the system?
It creates a set of symlinks so every program sees exactly the dependencies it needs.
https://nixos.org/guides/nix-pills/09-automatic-runtime-dependencies#automatic-runtime-dependencies
You can also create a container:
https://nixos.wiki/wiki/NixOS_Containers
Or you can create reproducible docker containers with nix:
https://dev.to/anurag_vishwakarma/a-better-way-to-build-reproducible-docker-images-with-nix-2k59
The secret sauce with nix is reproducibility. If it builds once, it will continue building exactly like that forever. Bit by bit.
That's very interesting, I was aware of how NixOS separated dependency versions but I didn't know it natively supported containers.
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.
What gets me is people migrating from VMs treating it like an entire host machine.
There is a lack of knowledge among developers regarding precompiling assets and classes (if interpreted), and people are trying to do too much in startup scripts.
Another thing I hate is wrapping the entire process in a script because people want to kill the main process without restarting the container. Yikes!
Docker exists because most programming languages don’t give a shit about producing easily executable outputs.
Nobody cares about your stupid python egg or ruby gem. How do I run it on my local?
Docker is still useful even for apps that compile to a single executable, as the app may still depend on a particular environment setup, particular libraries being available, etc.
How do I run it on my local?
spin a dock.....
Pack it with the interpreter in an executable.
Containers are a great way run applications.
Docker is a piece of garbage by a company way too far down the enshittification slide.
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.
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.
Nix has flakes; nix run can contain pretty much all of the needed dependencies. If that's not enough, you can set up an entire container as a module.
I wish I understood this because it seems funny
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
Moral of the story: never make breaking changes. Always backwards compatible, always.
It's worked for Windows?
When you're 90% of the market you get away with telling everyone else to suck your dick.
This meme but unironically
(Chorus) Heave ho, Docker, and sail the binary sea, With containers all lined up, so light and free. From the code to the cloud, we'll go with ease, In our trusty Docker ships, we sail the seas.
(Verse 1) Oh, the devs were a-struggling, in a stormy plight, With dependencies broken, things weren't quite right. Then Docker sailed in, with a promise so bold, Of consistent environments, as good as gold.
(Chorus) Heave ho, Docker, and sail the binary sea, With containers all lined up, so light and free. From the code to the cloud, we'll go with ease, In our trusty Docker ships, we sail the seas.
(Verse 2) We build and we ship, with our Docker compose, In our microservices, our confidence grows. With images light and containers so tight, We deploy in the morning, and sleep sound at night.
(Chorus) Heave ho, Docker, and sail the binary sea, With containers all lined up, so light and free. From the code to the cloud, we'll go with ease, In our trusty Docker ships, we sail the seas.
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).
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
Say Plasma "breaks" - a wiki will not help fast enough.
I'm not trying to defend rolling release for a gaming console, but give me at least the option to decide for myself whether I'm ok with breakage or not. There is this kernelspace NT driver that I wanted to try, but I couldn't because pacman is locked.
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.
hahahahahahaj I don't know if it is funny because it is absurd or if it is funny because there are some folks out there that really think like that hahahahah
This meme format works best to absurdly overstate the uselessness of something you find mildly annoying. That's when it's funniest, because the criticisms are grounded in something real, and the low-stakes controversy makes the aggressive tone funny in context.
I use podman and have absolutely no idea what I am doing. Send help
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.
very cool and based; I take it you're a chroot fan?
Reading about all the security issues in Docker lately, i'm thinking about using LXC via Incus/Proxmox. Should i? Or podman?
I just put my docker services in a lxc container. Docker is neat and lets me deploy shit without having to worry. Works pretty well, just remember to put your lxc containers on your SSD and not your raid mass storage (my hdds have errors now, fuck)
I need all of these! I already have them for data structures and agile but this is also golden!
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
