281 Mirantis Kubernetes Engine (formerly Docker Enterprise) Reviews
Application isolation.
Reusable containers so that we build it once in Jenkins, push it to a repository, and can then push it to other environments.
Smaller containers than a full VM. Review collected by and hosted on G2.com.
Networking can be hard, but it's being improved.
Service discovery can also be difficult.
Using containers for horizontally scalable applications like Cassandra, Zookeeper etc can be difficult. Review collected by and hosted on G2.com.
Docker is an excellent system for encapsulating all of the dependencies of a software package, so that it can be portably deployed either for development or for production. It uses technology derived from Linux containers to built a standard operating environment that collects only the resources that an application needs to work, and then networks together these containers to allow you to build services out of these components. Review collected by and hosted on G2.com.
The biggest challenge with Docker is keeping up with the rapid pace of development. The Github project has hundreds of open issues, and the pace of development is such that if you are using advanced features that you are likely to run into substantial changes at every major release. Review collected by and hosted on G2.com.
Easy deployment and getting rid of the dependency hell is the selling point of Docker. Once you setup your Docker environment (which can be a pain in the arse if it is your first time), all your colleagues can use varying development environments without worrying about build errors and portability. Review collected by and hosted on G2.com.
Depending on the OS, Docker may use different implementations to be able to act same on every platform out there. Current version therefore includes some workarounds for the sake of portability. Mac OSX and Windows version depend on a linux vm, FreeBSD version (unofficial port) use jails etc. Support is increasing but it would be good if we could use latest Docker with the same experience on every one of these platforms, especially on FreeBSD. Review collected by and hosted on G2.com.
Docker is very easy to use, versatile and reliable. The community also makes a big difference in the product, mainly due to Dockerhub that has many images available, for most of the products you can imagine. It is also great because you can push your own images. Another great tool is Docker Registry (now Docker Distribution) that enables every company to have its own image repository. Great tool!!! Review collected by and hosted on G2.com.
Besides its wide documentation, I feel it's a little bit confusing. It's difficult to know if an particular solution would apply to the user's version of Docker or also with a particular OS, like Mac OS for example. I also had some trouble with my version of Mac OS + Docker Machine + Virtualbox. If your environment is a pure Linux I think you won't have any trouble. Review collected by and hosted on G2.com.
The thing I love about Docker is consistency. Before Docker we had to think about environments, installations, configurations, etc and it was all a big mess. With Docker we still have to think about it but in a more organic, organize and consistent way. Review collected by and hosted on G2.com.
Seriously I don't know what I don't like about Docker. Maybe the fact that more people should be using it but that's nothing to do with Docker. Review collected by and hosted on G2.com.
Docker is a clean an elegant way to organize your development and testing environments. Also you get the deployment systems for free since it's the same container as your the one you develop. Docker helps you strip out the unnecessary elements of a system leaving you with a clean and complete (for your purpose) system. This fact saves many resources in the deployed version. Furthermore Docker is enhancing re-usability and maintenance. Review collected by and hosted on G2.com.
Documentation is not structured enough. You have to search all over the internet to get what you need. And still it helps you only until the intermediate level, while there are plenty more aspects in Docker that can make your productive reach the ceiling. Review collected by and hosted on G2.com.
Docker popularized the practice of running apps and services inside isolated containers. The underlying technology and practices were already available to a degree, but to use those technologies in a meaningful way, you once had to build quite a bit of tooling and infrastructure on your own.
Docker-the-tool makes this process easier using a friendly API and CLI, and because Docker-the-company is well funded, additional tools have emerged that make the process even simpler. For example, docker-compose lets you spin up an entire cluster of interconnected containers on your local machine using a single YAML file. Then, you can make some minor changes to that file, and use the Tutum service to manage deploying a cluster of production machines running those same service. Review collected by and hosted on G2.com.
There is still a lack of coherent documentation that describes how to build an entire stack of software, with horizontal scaling, zero-downtime deploys, and so forth. There are also some security-related anti-patterns that can be easily overlooked at first (such as using the "root" user inside a container).
It can also be difficult or impossible to work on "Dockerfiles" (build scripts for docker images) when you have no connectivity, limited connectivity, or bandwidth caps. This is due to a need to re-run the entirety of any step that was changed. For example, if you have a step that pulls in 100MB of packages, and you want to add one more package to that list, then rebuilding will cause the entire set of packages to be re-downloaded in the typical use case.
Finally, with some types of language ecosystems, it's difficult to run a development environment inside a set of containers while also using a hot-reloading environment. You can build and test containers locally pretty quickly, but that is still slower than not rebuilding at all in those types of development scenarios. Review collected by and hosted on G2.com.
Docker makes the process of getting through the domain knowledge about Linux Containers much easier than going through old, traditional methods. Throwing aside the need to juggle dozens of separate concerns, everything goes through the container system, giving you a simple CLI to create a large, dynamic system of interworking components simply.
In other words, Docker makes setting up new servers as fast as downloading a container from a repo and starting it. It also does it to a strength that traditional VMs just can't manage- Docker Containers are small, performant, and guaranteed rock-solid. Review collected by and hosted on G2.com.
Documentation when I wrote most of what I did with Docker was inconsistent, and half of it was contained on blogs somewhere on the internet. On top of this, the community can be a bit purist- if you're not doing things "their way", often other users whom you seek help from will throw up walls to getting the solution you need.
Also, there's a lot of obvious quality-of-life improvements needed throughout the software, but as relatively young software this is unsurprising, and the situation improved rapidly even in the months I was working on Docker project. Review collected by and hosted on G2.com.
Docker is a tool that allows for developers of all size to develop and deploy applications with confidence and in a streamlined manner. Docker images allow for the exact environment you develop on to be used in test and prod, reducing bugs from changing environments. The community is fantastic and there are plenty of resources for developers that simply want to manually "docker push" and "docker run", or perform enterprise level cluster management with tools like Kubernetes. Review collected by and hosted on G2.com.
Some of the tools in the Docker ecosystem-- the software that helps you actually *use* Docker in production-- is a little young. Tutum (recently purchased by Docker) allowed for even small developers to compose services and connect them together with software-defined networks and service discovery, but other self-hosted alternatives are still maturing. In essence, while the community is a strength, it is also a weakness-- it's in development and will still take time to fully develop. Review collected by and hosted on G2.com.
I am always interested in the development of software, Docker nonetheless. That means that I'm trying to watch the commit history very carefully on Github and so i will be ahead and aware of new features that will show up in the upcoming release. Review collected by and hosted on G2.com.
The toolkit around docker is rather large and sometimes there seems to be along way until you get to docker. You have docker-machine which can boot docker rather fast but lets take this step further. Now i want to boot docker on three different providers, add a scheduler (docker-swarm) and high-availability (a consul-cluster outside of docker) we are starting to get there but this is rather complex. I still miss scaling up and down depending on usage thresholds. Review collected by and hosted on G2.com.
