I dunno, most of my experience from Docker comes from docker compose, and it's "put this thing in a file and edit it and then run docker compose up -d".
So if anything, it's best illustrated with the old meme of a dog typing on a computer going "I have no idea what I'm doing".
How did they get the car in the van? I guess they drove it in, then crawled out the back while it was being transported? Probably wouldn’t be wise to sit in it because of carbon dioxide buildup?
All those backdoors
Source: Shico Rico Douga (NSFW site) by Deadnoodles
I can't judge but wow. Impressive
That's why they call us backend developers!
Turtrucken
Truvancar
they're one layer away from the bicycle
Honda Minimoto
Where did you get a picture of my docker containers running on my LXC containers on proxmox?
Only on Windows and Mac, right? On Linux it's just two layers, yeah?
It depends. At $dayjob I deploy compose on Linux VMs.
Oh, lol, well, I guess I mean 2 + N where N is the number of layers Linux is already on
The x86 CPU will be 2 additional layers
Yo dawg²
I dunno, most of my experience from Docker comes from
docker compose, and it's "put this thing in a file and edit it and then rundocker compose up -d".So if anything, it's best illustrated with the old meme of a dog typing on a computer going "I have no idea what I'm doing".
How did they get the car in the van? I guess they drove it in, then crawled out the back while it was being transported? Probably wouldn’t be wise to sit in it because of carbon dioxide buildup?
Or a wireless winch, if I were to hazard a guess.
And the database layer is a separate truck sorta welded onto the outer truck with varying degrees of weld quality.