This type of propaganda is an insult to human intelligence. What, the author is hoping that the readers underwent a lobotomy?
Or maybe, its so obviously wrong, it must be pure clickbait.
The demise of Docker and the rise of Kubernetes
61–70 of 101 posts
Re: The demise of Docker and the rise of Kubernetes
#62Docker is too simple and limited to make a living off it
Re: The demise of Docker and the rise of Kubernetes
#63> If you’re (only) a docker expert, you’re in troubles right now. There are no more jobs looking for docker expertise and you’re dangerously close to unemployable. This is such a silly and unrealistic argument - no one is a docker-only expert. And docker is a desirable skill, just not on its own. It's like saying that git-only experts are unemployable.
"docker-only expert" makes me LOL :)
Re: The demise of Docker and the rise of Kubernetes
#64The real world is still very much using Docker. Infact a few companies I've interviewed with this year aren't even using any kind of container setup and they're doing just fine and making money. This kind of article just adds to the Jonesing-for-shiny-things mentality that really doesn't do the engineering world any favours.
Pretty much I worked for an e-commerce, leader of their market, that used no Containers for the past 3 years. CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. We contemplated moving to ECS/EKS to stay "current" and to make test/development environments easier to create, but…
I would be interested in hearing you expand on this if you don't mind :-)
Re: The demise of Docker and the rise of Kubernetes
#65Docker has not built support for cgroups v2 - which has been available in linux for 3 years. https://github.com/opencontainers/runc/issues/654 in order to force this issue, Fedora has made cgroups v2 as default and mandatory in the new upcoming Fedora 31 causing docker to fail to run. https://github.com/docker/for-linux/issues/665 Podman (and other docker equivalents) have supported cgroups v2 for years. I suspect th…
Out of curiousity, have you seen anywhere using CRI-O/podman in production in place of Docker anywhere?
Re: The demise of Docker and the rise of Kubernetes
#66Docker is still pretty embedded in a lot of workflows, thanks in part to its use by-default in many Kubernetes distributions, and the popularity of Docker Hub - not to mention various tutorials and scripts which refer to docker tooling. But yep, I'd agree with the general premise here - with the emergence of tools like cri-o[0], podman and buildah (which let you build and ship container images without the need to run…
From what little I've looked at podman, the "no daemon, rootless" story isn't quite as straightforward as it might appear.
For starters, you couldn't expose ports as a standard user running podman last time I used it . Also every container got it's own conmon process, so there's still an overhead, it's just done differently.
Re: The demise of Docker and the rise of Kubernetes
#67This is like saying "The demise of Wheels and the rise of Automobiles"
Re: The demise of Docker and the rise of Kubernetes
#68The real world is still very much using Docker. Infact a few companies I've interviewed with this year aren't even using any kind of container setup and they're doing just fine and making money. This kind of article just adds to the Jonesing-for-shiny-things mentality that really doesn't do the engineering world any favours.
Pretty much I worked for an e-commerce, leader of their market, that used no Containers for the past 3 years. CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. We contemplated moving to ECS/EKS to stay "current" and to make test/development environments easier to create, but…
I can't help but feel that the drive towards docker-style containerisation was fueled by nothing more than the fad for developing on OS X. If you've got an environment where the devs are working on the same OS as production, it becomes much easier to adopt OS packages (whatever flavour that is) as the deployment mechanism, and as a side benefit it becomes easier to set up the dev environment in the first place.
I've done this with Debian, it worked great.
Re: The demise of Docker and the rise of Kubernetes
#69Docker is still pretty embedded in a lot of workflows, thanks in part to its use by-default in many Kubernetes distributions, and the popularity of Docker Hub - not to mention various tutorials and scripts which refer to docker tooling. But yep, I'd agree with the general premise here - with the emergence of tools like cri-o[0], podman and buildah (which let you build and ship container images without the need to run…
From what little I've looked at podman, the "no daemon, rootless" story isn't quite as straightforward as it might appear. For starters, you couldn't expose ports as a standard user running podman last time I used it . Also every container got it's own conmon process, so there's still an overhead, it's just done differently.
Fair point re: conmon, and yep, even in the strictest sense of the word, it is a daemon now that I read up on how it executes the container.
I guess it's better to say that only a monitoring daemon is required with this setup (rather than all of the additional daemon services that docker provides).
Re: rootless podman, it looks like there's a good resource to track progress here: https://github.com/containers/libpod/blob/v1.6.2/rootless.md - that must be a common ask, could be interesting to track.
(I'm definitely guilty of being overoptimistic about these tools, but do hope they improve because the principles behind them seem very sound)
Re: The demise of Docker and the rise of Kubernetes
#70> If you’re (only) a docker expert, you’re in troubles right now. There are no more jobs looking for docker expertise and you’re dangerously close to unemployable. This is such a silly and unrealistic argument - no one is a docker-only expert. And docker is a desirable skill, just not on its own. It's like saying that git-only experts are unemployable.
As a "docker expert" (I wrote a book on it [1], was one of the first people to get a Docker certification, and have gave multiple talks on it): please send help!
Except not really... The original article's writer doesn't know what they're talking about. If anything, knowing Docker has increased my employability in the new K8s-centric world.
1 - https://www.amazon.com/Deployment-Docker-continuous-integrat...