What container/virtualisation technology do you guys prefer?

Also I've been thinking of picking up either k8s or docker, mainly docker for ease of deployment or do you think it's wortb learning both perhaps? I do know they have a bit of different use cases

They are not the same, and most of the time you will use Docker with k8s

@Tounai so in the end one should just learn both or the very least docker, thanks for answering and not lgtfy boting me. Do you use any of those either professionaly or in your hobby projects?

@matt-jd You should begin with Docker, learn how it works with both CLI and docker-compose (try to deploy a postgres image for example, and then, a Keycloak instance), and try to make your own image. Then, you will be able to understand the benefits of k8s.
I actually work for two companies, one is using docker and k8s, the other none of these. The first is a start-up, the second a relatively old company. Even if docker and k8s are both great tools, they are not the solution to everything.

@Tounai thanks I think that I will try it they way to learn. While nothing is the solution for everything I do think it can really help in deploying erlang/elixir stuff on other machines/environments

Must admit I use docker because everyone else does, and not swayed from it.

Used K8s and AWS ECS for orchestration - the latter is simpler to set up and maintain, but doesn't have all the features of K8s, and obviously you're then tying yourself into AWS.

@matt-jd docker is build once, run everywhere solution. but... is also very usefull for a lot of things - for example, spinning up a temporary mongo instance, and doing some work with it. Then dispose the instance. Or playing around with redis. or elk. or a simple node app, with a postgres backend.

You can also use it to make code build faster, and cleaner. then pull the binary out of the image.

k8s is used to manage multiple docker hosts - learn what it is, but don't put too much effort into it.