Using Docker in a VM on a Hypervisor is industry standard, using docker inside of docker may be okay for CI purposes but I wouldn’t do anything more than that in production if it’s not necessary.
The stack from the image above (Windows>WSL> Docker>Minikube>Docker>App) is something you’d use on a dev machine (not a “real”, production-like test environment), in which case you don’t really care about the performance loss
Windows itself is technically running in a VM if you have Hyper-V enabled (not quite that simple, but that’s a reasonable approximation). Hyper-V is a type 1 hypervisor which means it runs directly on the underlying physical hardware, and both Windows as well as any VMs you create are running on top of Hyper-V.
I’ve ran Docker in LXC in a KVM before. I used LXC to have multiple containers on a VPS. Then I had to run something that works best with Docker, so I stuck Docker in an LXC.
It’s windows host because it has the unique property of leaking to higher levels of abstraction and leaking to lower levels of abstraction, which is a technological feat that can only come from Microsoft.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
TIL go is an interpreted language and runs straight from source code!
obviously the shell script compiles the executable every time the image is run :)
Docker, no docking!
Docker, no docking!
Docker, no docking!
Well… depending on the situation… it may be inappropriate [Urban dictionary - NSFW description warning]
deploying docker-compose to production
Wait, by docking do you mean… docking?
👉 👈
man touch
Backup, backup…
You know how much layers there are under hello.go?
There are even layers within the hardware layer. :)
and of course at the lowest level the particle interactions are all calculated by cueball using rocks in a desert
relevant xkcd
is this what you’re referring to?
yup
There are even several layers of transistors. And several energy layers of the electrons
Dora s’appelle Jane en anglais ?!
Non, Dora s’appelle Dora en anglais. The meme is just weird.
Non. Et effectivement Jane ça ferait pas très latina. Tous les autres stéréotypes sont là pour apprendre l’espagnol
Who’s Jane? This is Fedora the Explainer.
Could also be a hyper-v layer around Windows “host”
People don’t actually do this, right? Docker inside docker inside a VM inside another VM? On windows? Right???
I’ve seen docker inside a VM before but that was just a dev box for testing
That’s super standard for actual infrastructure
That’s the most reasonable part of the image
Are you not losing loads of performance by stacking vms like that?
Using Docker in a VM on a Hypervisor is industry standard, using docker inside of docker may be okay for CI purposes but I wouldn’t do anything more than that in production if it’s not necessary.
The stack from the image above (Windows>WSL> Docker>Minikube>Docker>App) is something you’d use on a dev machine (not a “real”, production-like test environment), in which case you don’t really care about the performance loss
Isnt that exactly what minikube is? Kubernetes in docker.
I’ve used docker-in-docker images, but its usually not fun.
I’m pretty sure docker recommends that it runs under WSL when on windows.
Windows itself is technically running in a VM if you have Hyper-V enabled (not quite that simple, but that’s a reasonable approximation). Hyper-V is a type 1 hypervisor which means it runs directly on the underlying physical hardware, and both Windows as well as any VMs you create are running on top of Hyper-V.
Oh that’s an interesting tidbit, didn’t know that
Yeah, docker in a VM makes sense. Docker in docker in a vm in a vm though?
Yep, can confirm
I’ve ran Docker in LXC in a KVM before. I used LXC to have multiple containers on a VPS. Then I had to run something that works best with Docker, so I stuck Docker in an LXC.
It’s windows host because it has the unique property of leaking to higher levels of abstraction and leaking to lower levels of abstraction, which is a technological feat that can only come from Microsoft.
My abstractions are:
inb4 it’s actually some microcode change introduced to intel management engine