Docker/kubernetes

I wanna add to the replies by saying that docker-with-k8s is also good for spinning up multiple copies of the same thing for load distribution.

Oh also, one big warning: if you're running Docker containers for a non-systemd OS on a systemd host, certain things get fucked up. For instance, you can't get coredumps from the container, because when a process crashes it looks at /proc/sys/kernel/core_pattern for where to put it. Since this is inside a container, the /proc/sys variables are coming from the (systemd) host, which tells the process to write it to some systemd-specific directory which isn't present in the container's filesystem. You can fix this by sysctl'ing kernel.core_pattern on the host, but it's a stumbling block.

The startup I used to work at used a Kubernetes cluster with Docker containers

Never used these, where do i start?

Can't you put a custom core_pattern file in the image?

>The whole point is to allow multiple devs to work on the same app and know whether or not a problem exists
No it isn't, it's because web devs are lazy shits who can't be bothered to properly manage dependencies.

>once you have a good container image you can run it anywhere.
L
M
A
O
It's definitely useful but it's far from the silver bullet retarded shills make it out to be.

It is a vastly superior experience to pretty much anything else out on the market.

Why the fuck would I want to use a VM instead? It offers no additional utility, and only complicates things leading to useless jobs like more Sys admins.

not the same thing.

It might be cool for someone who is testing and is just pulling those images out of docker.hut but recently I had to create my own images for a project and this shit is a pain in the ass. Its like doing things blindly because the resultant container must run and auto configure without manual intervention.