Containers Explained
Containers Explained
27 comments
-
To be fair Kubernetes creates copies of the things it drops into the ocean to replace them as fast as they’re lost.
-
I'd say that docker compose also has the containers strapped together with holes cut in the walls between them for communication.
Kubernetes is more the crane that stacks the containers onto passing ships instead of a singular ship itself.
-
Seriously! There's no network, NAT, port forwarding, network isolation - hell, not even any iptables rules in any of these images. This meme makes no fucking sense.
-
-
-
Now add VMs and proxmox
-
The ocean is fake
-
ECS/EKS: The ocean belongs to someone else.
-
-
-
Each container sk8s right off the deck.
-
Kubernetes is more stable than docker compose. Docker compose is fishing for containers after the ship capsized. Frustrating and nothing works out of the box.
-
Huh? All my docker compose projects work fine 'out of the box', the oldest ones have been stable for years now.
-
I personally really enjoy interacting with docker compose and I've successfully used docker compose to get a 0 downtime setup on my company's internal web servers by using a reverse proxy
-
Docker Compose brought "works on my machine" to the cloud.
-
-
Suddenly, thousands of sneakers wash ashore all over Ireland and everybody is trying to pair them up.
27 comments