281 Mirantis Kubernetes Engine (formerly Docker Enterprise) Reviews
Docker enables us to leverage Containers to create disposable, immutable and a consistent infrastructure for our Developer teams. The user experience of using Docker and the related workflow is fantastic. The learning curve is not steep, allowing our developers to adopt it quickly in their development process. The Docker ecosystem is extensive, allowing us to invest in using and building tools that powers our Continuous Delivery Pipeline. The simplicity of the product is the best part of the overall experience. The pace of innovation in Docker and the related community allows us to focus on providing better developer experience at all times. Review collected by and hosted on G2.com.
We had issues with Docker on different file system drivers like DeviceMapper. (AUFS works for us without issues right now). Also, we are not using Docker for persistent services like Database that requires us to use Host volumes. Docker's support for persistent containers is still patchy, and is not a permanent solution. Rather we would invest on using Distributed shared file system to be able to sustain persistent containers. Concurrent Docker image pulls also fail for some file system drivers used with Docker. Security assessment of Docker images is still in very early stage, and is something that is causing friction with our Security teams for mass adoption. Review collected by and hosted on G2.com.
Easy to spawn new environments for testing, using container images identical to those already running on production systems to easily reproduce problems found in production. Also it enables for quick and easy setup of development environments, without the hassle of explaining everybody how to configure a web-server or other software. Review collected by and hosted on G2.com.
This stateless stuff is all cool but it has some drawbacks.
Sometimes there are security updates, just tiny updates, but if you want to update them the normal way to go is to actually rebuild the whole container, and maybe upload a few hundred megabytes of data to a few dozen servers, this gets really annoying, and there doesn't seem to be any nice solution to this. Review collected by and hosted on G2.com.
The best way to eliminate typical dev / testing / prod environment issue
Simplified the deployment practice for most service systems.
Also contains a large number of pre-built images includes most frequently used services, nginx, mysql, etc. Implemented a new way to setup a service with nearly 0 impact on the host.
Review collected by and hosted on G2.com.
Different running model compares to traditional software development / deployment method
Introduced a little complicated management of networking / storage
Difficult to remote manage / monitoring
Resource sharing between containers or hosts is complex
The docker hub is limited to free user, can only have one private image
The private image repository / registry is a little complex to setup. Review collected by and hosted on G2.com.
The reproducibility for developers. Got a bug in production? Simply take a copy of the container running in production, load it on your desktop, open up a few ports, and start debugging. Review collected by and hosted on G2.com.
The ramp up time and mental model is pretty heavy. It is not like running an application on your desktop. Pretty much anything that you have done developing on your desktop is quite different such as mounting a drive, connecting to a socket, etc. Review collected by and hosted on G2.com.
There are two features that I really love about Docker:
1. My development environment and production environments are the same, because both environments are running the same container.
2. Deployments are easy and the same deployment can be used by any team that deploys Docker containers. Review collected by and hosted on G2.com.
The biggest pain points I've had with Docker are:
1. Network issues: Sometimes networking can be confusing when you're running a container.
2. Uploading Docker images to your Docker registry: the images can be quite large. And, given that they use a union file system, you can run out of i-nodes which can be surprising Review collected by and hosted on G2.com.
I really like that I can download and distribute software that I know is guaranteed to work without any distribution specific differences. Review collected by and hosted on G2.com.
A minor annoyance when installing software is that I have to specify what repo. It would be nice if I could just tell it to install a package and if I didn't specify repo it would prompt from some of the most popular ones. Review collected by and hosted on G2.com.
Makes it quick and easy to deploy software on Linux. Tools available make building tiny, sandboxed, secure packages a breeze. Allows me to be confident that my services will run exactly the same way on my laptop and on my server. Review collected by and hosted on G2.com.
Docker Hub is sometimes slow. Docker Private Registry is extremely unreliable when backed by S3. Docker Private Registry is not horizontally scalable. Docker is not truly "run anywhere" because it's architecture and OS-dependant. Much of the community is following poor practices by using Ubuntu as their base image, creating images that are far too large.
There is not yet a really good way to handle shared disk (such as NFS) Review collected by and hosted on G2.com.
Application level containers. You can quickly setup and system by spinning up the various images, without lengthly installation or setup.
For e.g., you can quickly get a nginx, redis, hapi server, and mongodb up and running in a matter of minutes. Review collected by and hosted on G2.com.
Docker is still fairly new, and bugs can be found here and there, and still lacking in some features. But in general, there is very little to dislike. Review collected by and hosted on G2.com.
That its popular, free, and open source! There's a huge community backing for it, and any help you need is usually just a Google search away. There already exist many containers for the typical software stacks that you might need: nginx, nodeJS, Postgres or MySQL... And if it doesn't exist yet, you can make your own. Review collected by and hosted on G2.com.
As with any new deployment technology, it takes a bit of a learning curve. Not a large one, but typically when you introduce a new layer of tech to your colleagues, they might groan due to the fact that it's once again another layer they have to deal with. Yet I feel that it's worth going through the effort to learn it. Review collected by and hosted on G2.com.
The ability to build a container that will run the same anywhere is immensely useful and just feels like the correct way to deploy software. This is a transformative concept that can help improve many aspects of software development within an organization. Review collected by and hosted on G2.com.
Docker hub is very feature light right now. Currently it just stores images, which it does very well, but it would be nice to see some integrations with service providers that can run the containers. This seems like a good area for Docker (the company) to expand their paid offering. It was a bit of a pain for me to figure out how to run a container on Amazon and Google as it required learning all about their proprietary products. It would be a nice benefit if Docker Hub had some ready-made integrations to click a button and have the container run (and dynamically scale) somewhere. This of course is a separate matter from the actual Docker software, but it would make the paid offering worth more if such functionality were included. Review collected by and hosted on G2.com.
