Docker vs. Helm

You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.

Incentivized

Deployment of helm charts is really fundamental to any software packages to our Kubernetes/docker containers, and without Helm, I cannot imagine how else to manage software components upgrades. When it works, it works great, when it doesn't - the world has not come to an end, there is rollback, and it's great, but troubleshooting does take time. And there is a learning curve. But it be worth it.

Incentivized

• Kubernetes context switching - very handy
• Integrate well and seamless - No complicated setup and or UX
• Ease of updating images and etc - very important

Incentivized

• Infrastructure duplication
• Customization of environments
• Applying of security updates

Incentivized

• It will be nice to see an admin UI for configuration of images
• Container networking can be simplified
• Data storage/volume management can be simplified

Incentivized

• It would be great if there is verbose mode in Helm errors. Not sure if it's a thing. But more detail in the errors do helps, at times.

Incentivized

I have been using Docker for more than 3 years and it really simplifies the modern application development and deployment. I like the ability of Docker to improve efficiency, portability and scalability for developers and operations teams. Another reason for giving this rating is because Docker integrates CI/CD pipelines very well

Incentivized

Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.

Incentivized

Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.

Incentivized

We didn't really need support, but the open-source community seemed responsive and informative when it came to issues. Many cloud native consultancy companies (including ourselves) offer support for Helm.

Incentivized

We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we defined a docker file which will be our base image and we performed all our activities inside that image to build infrastructure using terraform. Integration we have done in our gitlab pipeline and finally we remove the docker image so that the space can be reclaimed immediately.

We have a natural trending to use what is a reference in its space and Helm has being leader in its area for a long time. Since it has all features we need didn't make sense to us to invest time on researching and testing other alternatives, so Helm was our first and only tool in regards of automating deployments on Kubernetes

Incentivized

It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.

Incentivized

• With Docker adoption, were able to reduce 40% of the time taken to complete workspace setup
• Provided the environment packaging / configurability capability which enabled resource sharing and interoperability across teams
• Were able to leverage off the shelf images provided by leading product companies which increased reliability and security exponently

Incentivized

• developer velocity
• uptime

Incentivized