Docker's Second Death

Re:Docker's Second Death by polskibus on Sunday December 06, 2020 @05:29PM (#25327250)

Does it mean that developers working locally with containers should ditch Docker and Dockerfiles altogether?

If so, what should they replace it with, esp, if all you want to deploy to prod is contained in a single docker-compose? Is switching local development to kubernetes a good idea in terms of performance, fast feedback loop, development experience (smooth flow), etc. ?

[ Parent | on HN ]

Re:Docker's Second Death by tariqislam_ on Sunday December 06, 2020 @06:31PM (#25327709)

Author here. In the last part of my post, I do mention that Dockerfiles are probably the one thing that will outlast everything else from Docker. There's nothing really practical to replace that artifact at this time if you ask me.

There are some tools to convert your docker-compose into the k8s resource model. I'd advise against switching local development to Kubernetes. Docker found a sweet spot there, as heavyweight as it is today. I think where we'll land is Dockerfile + one of the other alternatives like kaniko, buildah, etc.

[ Parent | on HN ]

Re:Docker's Second Death by jacques_chester on Sunday December 06, 2020 @06:50PM (#25327820)

> There's nothing really practical to replace that artifact at this time if you ask me.

I am required by law to spruik Cloud Native Buildpacks. For most uses, I feel Dockerfiles are not necessary or desirable at this point.

Disclosure: I've been around CNBs for a while for Pivotal and now VMware.

[ Parent | on HN ]

Re:Docker's Second Death by tariqislam_ on Sunday December 06, 2020 @09:39PM (#25328856)

Haha, ok that's totally fair. Valid point. Thank you for bringing this up. I'd not considered them.

[ Parent | on HN ]

Re:Docker's Second Death by zapita on Sunday December 06, 2020 @06:43PM (#25327783)

No. Nothing will change in terms of support for Dockerfiles or support for running Docker images. The whole thing is massively overblown.

[ Parent | on HN ]