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.
Not just OSX: anyone using WSL on windows is an offender too
But as a WSL user, dockerised Dev environments are pretty incredible to have running on a windows machine.
Does it required 64 gig of ram to run all my projects? Yes. Was it worth it? Also yes
I’m even worse, I have used wsl in a windows vm on my mac before haha
I work in a windows environment at work and my VMs regularly flag the infrastructure firewalls. So WSL is my easiest way to at least be able to partially work in my environment of choice.
My experience using docker on windows has been pretty awful, it would randomly become completely unresponsive, sometimes taking 100% CPU in the process. Couldn't stop it without restarting my computer. Tried reinstalling and various things, still no help. Only found a GitHub issue with hundreds of comments but no working workarounds/solutions.
When it does work it still manages to feel... fragile, although maybe that's just because of my experience with it breaking.
I found the same thing until I started strictly controlling the resources each container could consume, and also changing to a much beefier machine. Running a single project with a few images were fine, but more than that and the WSL connection would randomly crash or become unresponsive.
Databases in particular you need to watch: left unchecked they will absolutely hog RAM.
You can cap the amount of cpu/memory docker is allowed to use. That helps a lot for those issues in my experience, although it still takes somewhat beefy machines to run docker in wsl
Image Transcription: Meme
A photo of an opened semi-trailer unloading a cargo van, with the cargo van rear door open revealing an even smaller blue smart car inside, with each vehicle captioned as "macOS", "Linux VM" and "Docker" respectively in decreasing font size. Onlookers in the foreground of the photo gawk as a worker opens each vehicle door, revealing a scene like that of russian dolls.
I'm a human volunteer content transcriber and you could be too!
Just need to put a JIT compiled language logo inside the blue car and caption it as "Containerise once, ship anywhere".
Hoping somebody organizes a /c/TranscribersOfLemmy or /m/TranscribersOfKbin
Add a JVM just for the hell of it
A foldable bike in the trunk
I mean I have Debian running an Ubuntu VM running docker. It's VMs all the way down baby
Does docker really spin up a VM to run containers?
Yes, under windows and osx at least.
Is that still true? I use Linux but my coworker said docker runs natively now on the M1s but maybe he was making it up
I suspect they meant it runs natively in that it’s an aarch64 binary. It’s still running a VM under the hood because docker is really just a nice frontend to a bunch of Linux kernel features.
docker is really just a nice frontend to a bunch of Linux kernel features.
What does it do anyway? I know there's lxc in the kernel and Docker not using it, doing it's own thing, but not much else.
I can't remember exactly what all the pieces are. However, I believe its a combination of
My understanding is that all of the neat properties of docker are actuall part of the kernel, docker (and podman and other container runtimes) are mostly just packing them together to achieve the desired properties of "containers".
Docker requires the Linux kernel to work.
M1 is just worse arm. Since most people use x86_64 instead of arm, docker had to emulate that architecture and therefore had performance issues. Now you've got arm specific images that don't require that hardware emulation layer, and so work a lot better.
Since that didn't solve the Linux kernel requirement, it's still running a VM to provide it.
When I was in school I once used a IOS emulator running inside a docker container of MacOS running on a linux machine. It works surprisingly smoothly.
The difference between Docker and a VM is that Docker shares a kernel, but provides isolated processes and filesystems. macOS has a very distinct kernel from Linux (hence why Docker on macOS uses a Linux VM), I would be shocked if it could run on a Linux Docker host. Maybe you were running macOS in a VM?
Nope, Mac OS as a Docker container, it's a thing: https://hub.docker.com/r/sickcodes/docker-osx
Also you don't need a Linux VM to run docker containers on a Mac host btw
The first layer in that docker container is actually KVM. So you run the container to run kvm, which then emulates osx.
Can someone please explain me like i am 5 what is docker and containers ? How it works? Can i run anything on it ? Is it like virtualbox ?
Think of a container like a self contained box that can be configured to contain everything a program may need to run.
You can give the box to someone else, and they can use it on their computer without any issues.
So I could build a container that contains my program that hosts cat pictures and give it to you. As long as you have docker installed you can run a command "docker run container X" and it'll run.
Well, I wasn't the one asking, but I learned from that nonetheless. Thank you!
A container is a binary blob that contains everything your application needs to run. All files, dependencies, other applications etc.
Unlike a VM which abstracts the whole OS a container abstracts only your app.
It uses path manipulation and namespaces to isolate your application so it can't access anything outside of itself.
So essentially you have one copy of an OS rather than running multiple OS's.
It uses way less resources than a VM.
As everything is contained in the image if it works on your machine it should work the same on any. Obviously networking and things like that can break it.
Is it like virtualbox ?
VirtualBox: A virtual machine created with VirtualBox contains simulated hardware, an installed OS, and installed applications. If you want multiple VMs, you need to simulate all of that for each.
Docker containers virtualize the application, but use their host's hardware and kernel without simulating it. This makes containers smaller and lighter.
VMs are good if you care about the hardware and the OS, for example to create different testing environments. Containers are good if you want to run many in parallel, for example to provide services on a server. Because they are lightweight, it's also easy to share containers. You can choose from a wide range of preconfigured containers, and directly use them or customize them to your liking.
Don't forget the ARM64 to AMD64 conversion.
This was one of the reasons we switched to docker in the first place. Our Devs with M series processors spent weeks detangling issues with libraries that weren't compatible.
Just started using Docker and all of those issues went away
it's like an automotive turducken
But it's Unix-like!
Uses a Linux VM for all the assignments anyway.
macOS is not unix-like, it is literally Unix.
Now add dind
Time to check out Podman.
Podman on MacOS is the same, is it not? Running a containers inside a VM?
Podman does the same. Podman runs fedora.