Live data from Hacker News

Docker's Second Death

tariqislam.com

61–70 of 286 posts

Re: Docker's Second Death

#62

I enjoyed the following: > Though it [Docker] does live on strongly within CI/CD ecosystems and, ostensibly, the inner loop of development thanks to the de facto standard Dockerfile. Docker will still live on for both Windows and Mac developers. As a platform for running production code it might be dead or dying, but as an ecosystem and a development tool it will continue to live and probably thrive. Docker is still…

A bigger issue is the fact that they were not able to become a unicorn despite having a tremendously popular product. It means there is no money in development tools innovation. This is not a good thing for the software community as it means all tooling innovation will only done and controlled by the FAANGs.

Re: Docker's Second Death

#63
post #43
post #22

Even though Kubernetes won't use Docker inside anymore.., Docker is still a very good piece of software for easily running Linux images on Windows and Mac. Dockerfile is still the easiest way to build images (even though now there are alternatives to docker build such as buildah). docker-compose is still a very simple way of running containers locally if you don't need kubernetes (e.g. on my raspberrypi for running h…

After they released local kubernetes support for the docker mac client, I've stopped using docker swarm completely. Although to be fair, I didn't use it all that frequently anyways. If your language runtime supports testcontainers ( https://www.testcontainers.org/ ) I would strongly suggest using that over docker compose. Docker compose is so lacking in features that I would just write bash scripts to setup/tear down…

What features do you find missing in compose?

Re: Docker's Second Death

#65
The article and some of the comments are a strange take. There is a place for docker. There is a place for Kubernetes. They dont have much overlap in my mind.

If I want to run an elastic production system with many components, and scale each component independently, i'd use Kubernetes.

...But if I want to run a Jupyter+PyTorch stack easily w/o wasting half a day on CUDA library dependency issues, I would use Docker without Kubernetes -- because I dont want to go down the rabbithole of

1. Installing kubernetes on my laptop

2. Ingress Controller hell

2b. Ingress Controller route/path/url annotation hell to make something like Jupyter work in Kubernetes

...when I can do that in 5 minutes with docker.

Re: Docker's Second Death

#66
post #22

Even though Kubernetes won't use Docker inside anymore.., Docker is still a very good piece of software for easily running Linux images on Windows and Mac. Dockerfile is still the easiest way to build images (even though now there are alternatives to docker build such as buildah). docker-compose is still a very simple way of running containers locally if you don't need kubernetes (e.g. on my raspberrypi for running h…

It's worth noting that dockershim isn't actually getting removed at the moment, it's being deprecated (so a warning will pop up in kubelet logs) and there's no fixed date for actual removal.

At the same time Docker/Mirantis have committed to creating a CRI plugin for Docker, so it seems pretty likely that Docker is and will continue to be an option for Kubernetes clusters.

Re: Docker's Second Death

#67

I feel like I'm missing some key insight here. To me, the tl;dr of this post is: Kubernetes removed the need for Docker just to run container images in a k8s cluster, ergo, Docker is dead. But Kubernetes is super complicated . The author seems to assume that everybody wants to run everything in Kubernetes, but if I want to run some backend on some server (or maybe on a few servers), then it feels like extreme overkil…

For small-ish setups, Swarm is still great. The cost of abstraction, and cognitive load, that k8s brings is greatly played down during discussions, and I feel it's quite a dangerous game to be playing.

The overhead with Swarm though, is low, and I like it. Where possible though, I'd also recommend having a look at ECS Fargate. Make it someone else's problem.

Re: Docker's Second Death

#68
post #30

Kubernetes is and will be a solution to a problem most organizations don't have.

Like scaling and fault tolerance? :)

You can do scaling and fault tolerance without a mesh networking approach. We've been doing it for a long time, even including containers as app delivery.

Re: Docker's Second Death

#69
I just want to make absolute sure that this is NOT the case. Does this mean that docker images built with `docker build` and pushed up to dockerhub will no longer be useable in kubernetes or not?

Re: Docker's Second Death

#70
post #56

What do they mean by “GA”?

GA means general availability. This usually means the first release containing new features, excluding beta releases. It is intended for mainstream consumption and more stable than beta. Maintenance releases come next. They fix bugs in features but generally don’t release new features.

Of course, such nomenclature and how strictly it’s adhered to varies from project to project.

Post reply on HN