Docker Reviews

Docker has proven to be a fairly efficient and stable virtualization platform for productive environments of high stress and traffic flow. The compatibility with other work tools is almost 100% guaranteed and also allows testing and deployments at speeds never before reached by infrastructure departments. One of the most significant advantages is the large repository of images of applications that are available in the docker hub. Without a doubt, of the best tools that I use in my day to day

It takes great knowledge of linux and infrastructure to use docker, it is not a tool for beginners, if you do not have the basic knowledge of a LAMP or LEMP for example, you can not deploy a disconnected application in docker, much less create base clusters of data, among many other things.

I appreciate Docker because it allows me to quickly and easily deploy applications in a consistent environment, no matter the underlying infrastructure. Its containers package applications and their dependencies together, making it possible to deploy them in any setting such as on-premise, cloud, or hybrid. Moreover, Docker makes scaling applications easy by replicating multiple containers. Additionally, it offers an efficient way to manage application dependencies and isolate applications from each other, simplifying the process of troubleshooting and maintenance. To sum up, Docker is an ideal tool for quickly deploying and managing applications in a consistent environment.

One of the things I least like about Docker is that it can be difficult to troubleshoot, especially when it comes to networking issues. Additionally, it can be a bit clunky to set up and configure for more complex applications.

The best thing about docker is docker cloud. You can host your application in docker cloud and share with your teammate or make it public which make it extremely helpful to install your application in literally any system without worrying about the system dependencies. Lots of contributors are there in docker cloud. Also helps you in improving your software infrastructure by isolating your application micro services.

Not more documentation about different ways to deploy application. Not good documentation about different commands you can run on docker-compose and their dependencies. Some time you feel stuck while solving particular problem and you find no help in the internet.

If your team is looking to streamline the onboarding process for new developers, Docker is an indispensable tool. By packaging the development environment into a container, it's incredibly easy to spin up a new instance for each developer, saving significant time on the initial setup. With Docker, you won't have to worry about the details of how each developer's environment is set up, making it an essential tool for any team that values efficiency and productivity.

One significant challenge with this platform is its steep learning curve. If you are inexperienced, it can be difficult to justify the amount of time required to get everything running correctly. However, once you've invested the time to become proficient with the platform, it offers powerful capabilities that can significantly enhance your productivity and efficiency. Therefore, while the initial learning curve can be a hurdle, it's ultimately worth the investment for teams or individuals seeking a robust tool that can help them achieve their goals.

Docker makes it simple to run applications in reproducible containers, eliminating the need for manual configuration. The containers can be integrated with many other tools and platforms, making it easy to use in a variety of different environments and setups. This includes popular tools like Kubernetes and Jenkins, allowing users to build complex but stable, scalable application environments. Because of its popularity, you'll certainly find a Docker image for any application you'd like to run containerized.

Docker containers use more resources than natively installed applications, which does impact performance. This is however something to expect from containerization. Additionally, the learning curve for more advanced setups (and sometimes even the simpler ones) is quite steep.

Before using Docker, it was quite difficult to deploy multiple instances of my application on different machines. I had to remember all the libraries and dependencies I was using. Also, it was really hard if the client was using different operating system than I was! However, with Docker, these problems are solved, I quickly deploy my applications on other machines without worrying about their infrastructure configuration.

Despite all its potential features, Docker remains insufficient and complex alone, since if multiple docker containers are deployed together it is hard to control and monitor all of them, hence the need to use an orchestration tool. Personally I use Kubernetes.

Generating an image for the project will aid in deployment and ensure a consistent environment across all systems.

With new CPU architectures, container networking is difficult and requires privileged access incompatible for a while.

The main benefit of docker is that it ensure the applications runs the same way on any machine. Dockerized applications can be easily moved between different environments without any compatibility issues. Also we can run multiple containers on a single machine making the most efficient use of available resources. Docker containers can be quickly deployed and scaled. Very lightweight and portable.

There is a learning curve associated with Docker, particularly for developers who are new to containerization. Docker is designed to work with modern, cloud-native applications, and may not be the best choice for older, legacy systems.

docker allows you to test applications without having to install them. it allows to make POC quickly and to choose the right application.

Sometimes is better to use unix container :-(

Some challenges we are facing in implementing our project in the production environment, not meeting every compatibility and version we are using in production, so docker came up with this solution where we make one image with all our version control and it works on direct development so this is amazing about docker, it has many features and we have GUI also for docker were we can manage our docker images and maintain that thing we are implementing in our image

We face some issues while using docker is, in the beginning, we are working with docker CLI where we need to remember their commands so this is hard in beginning but after use, we are familiar with this, docker GUI version is very big so t take too much memory for control that thing, we also have another product which makes easy of that thing is portainer, you can check out this also

I find very convenient the way I can ship a demo by creating a docker image with all what is needed inside. I am more tended to the idea of a container serving a single purpose, but in much cases docker can be used to package and ship all that is needed to have a not complex MVP, even if it was complex several docker images can be built, but talking about simple cases I found docker easy of use by...

Read more

IMO the user experience for a developer is more easy in linux based environments than in Mac environments, or it also could be that the development environment provided by some companies is some kind attached to mac computers but then on the testing, deployment, and production environments is more linux based. So the experience is not kind of uniform in my opinion.

Simple to install and setup. I'm currently using Docker Desktop for the MacBook Pro M1. In production we run docker engine on Ubuntu. The docker ecosystem is fairly robust, it's easy to find an official docker image for any popular software product. While I mainly use the CLI, the UI is simple and easy to use for new users. Once you have experienced the convenience of launching a docker container and letting docker manage the runtime and all dependencies, it's hard to go back to virtual machines and configuration scripts. Docker is regularly updated with new features and updates and the update process is also very simple.

There is somewhat of a learning curve when building your own Docker images. Docker does have a fairly heavy footprint as when it is launched it also creates a QEMU process. Depending on how much RAM your system has, this can be up to 8GB. It would be nice to have an auto clean option as I found that Docker images started to consume a lot of my storage space. If you are using Docker for work, you may be obligated to pay under their new terms of usage.

Ability to spin up software with just a few clicks. Initial setup doesn't require to much experience. Downloading new images and containers creation gives a lot of joy. It's a great way to perform POC and experiments as if they appear to be invaluable the removal from the device is simple and doesn't leave any orphaned dependency packages. Scaling services through Swarm allows to greatly improve performance of applications that can work in such environment. There is a huge variety of systems on which it could be run.

By default the docker service storage is kept on /var (on linux systems) which doesn't usually tend have a lot of free space. The amount of documentation available could be overwhelming in the beginning. If you would change the storage driver on an existing docker environment you will loose all your containers and images. If you would like to keep them you need to import and export them manually. There are some security concerns and it's easy to expose yourself if you don't know what you're doing.

Docker allows us to containerize our applications - meaning that pieces of big application can run in isolation, without having to set up dependencies on any environment. It allows us to worry less about server configuration, setup time on individual machines and not have to worry about dependency management. In conjunction with Kubernetes, it works great to deploy containerized applications to facilitate microservice/microfrontend architected applications

Docker has a steep learning curve. Configuring Docker desktop itself is a pain, although it becomes easier to containerize applications once the setup is complete. It requires a great deal of RAM , and thus, nearly impossible to work, on low RAM laptops.

Docker is the most popular container tool that helps teams set up and mange environments to run their applications without having to resort to VMs. It provides a simple interface to create environments and test, deploy and maintain applications within local, on-prem or cloud infrastructure. It has an extensive community that builds Docker images, pre-built environments that support for a variety of operating systems, programming languages and tools.

Docker can have a somewhat steep learning curve and is hard to explain to someone who doesn't know about it. Some of the more nuanced configuration options can be hard to find and harder to understand for newcomers. The support for Windows environments is also not as extensive as it could be.

Easy to use, great documentation, wide support in all major cloud providers and OSes (both regular and NAS oriented), lighter on resources than even the lightest VM. Great for web-specific microservice-oriented solutions deployments. Supported by all CI/CD platforms.

Security/privilege requirements of running the dockerd daemon.It's being dropped for CRI-O in Kubernetes deployments.

High adoption rate across multiple platforms and major vendors. Microsoft and major linux flavors support Docker. Lots of documentation and deployment guides online, and plenty of IT professionals have adopted the tool. Lots of contributors are providing images and documentation to get you started with many popular applications and software. Great scaling design that considers running Docker across many different servers, and does a good job at making the deployment generic, where an Administrator does not have to hard-code specific file paths for a given server. But rather, they can generalize their deployment commands to work on many servers. Flexible shared resource design with volumes makes sharing config file across multiple containers/servers easy.

Be careful with images provided by the community. Some images have poor documentation, or function strangely. Be sure to test each image. Recommendations to some command syntaxes may cause some confusion for new administrators. Ultimately, these revisions create options for and admin, but I found it a bit confusing determining which options were the best practice, and for what reasons.

Easy to deploy application with one single commandNo need to configure services again and againEasy to allocate resources(Ram/CPU) per containersVolumes can be created to manage offline(mounted) files(reused)Applications can be containerised and we can create image, we can share the push this image to central repository/Docker Hub, then it can be pulled on any nodes to create copies of applications for faster deployments

Cant be used for continuous integration and docker dont assure of availability as if container gets down all the services inside container gets down, which cannot be automatically orchestrated on creating new containers for high availability

Docker is one of the best containerization application. To achieving continue integration it's very helpful. Managing the deployment container and images is now easy with Docker. Docker help to do the things for you by automation. Once you configure a Docker in your environment it will make sure that issue will not occur due to development or production environment. It also very helpful in deployment and virtualization. The best thing in it is secure and transparent as it's source code is open.

As docker can be configure in all environment and architecture, but it is sometime very challenging to solve the particular issue that is making hurdle in configuring it. Documentation is also limited as it is not covering all the aspects or environment in which we or our organization is working. I feel they should also provide the some enterprise feature like image management in open source version also.

Docker made the deployment across a heterogeneous ecosystem very easy and much faster than before. Helped integrate across diverse platforms with less effort on my part.

Mini-docker containers were a little difficult to manage and the app didn't include free software to manage them. What good is a technology that lets you package and ship out the apps without giving you a way to mange them as well?

The best thing about docker will be docker cloud. You can have your application in docker cloud and offer with your colleague or make it open which make it to a great degree accommodating to introduce your application in truly any framework without agonizing over the framework conditions. Heaps of supporters are there in docker cloud.

Not more documentation about various approaches to send application. Not great documentation about various directions you can keep running on docker-make and their conditions. Some time you feel stuck while taking care of specific issue and you discover no assistance in the web.

Dockers containers are lightweight and portable, making it very easy to run multiple applications on the same host or move them between different environments.The ecosystem (Docker Hub) and extensive use in the FOSS community makes it easy to share, configure and deploy images.Lastly, Docker containers automatically start after a system reboot without any trouble, which is very nice.

You will need to be familiar with the command-line interface and the linux filesystem to be able to utilize docker in any meaningful way, even when using Docker via the Docker Desktop GUI.

insanely powerful and easy to use, great for almost any use case

There's a learning curve but that's for everything

I love how testable docker is outside of needing to spin up a new server every time you make a change to a dockerfile build. This way, I can iterate very fast on any changes I want to make and have the benefit of caching old steps in the build to make it even faster locally.

This is a problem more because we have been using docker for many years, but the offerings have changed recently in terms of how you run docker on Mac vs Linux causing the old instructions of how we used to install the software and VM on our machines (docker-machine) to be outdated. This has caused issues with installing it on newer employees computers but we just need to accommodate ourselves to how the new deployment infrastructure of docker for mac works.

It is the most advanced and most mature way to create, deploy and maintain application containers. It has alot of features out-of-the-box, including native container orchestration with Swarm, but there are also a multitude of official and 3rd party plugins to add. The Docker Engine is extremely fast and all commands are built up very logically (if you know a few commands, you can intuit the rest of them very easily).

There is a bit of a learning curve in using the software. The other downside (which is minor) is that because the software has changed alot in the last few years, the non-official documentation is out-of-date. This means that reading a 3rd party blog post that is only a year old is almost useless. This, coupled with the fact that the official documentation is not great, results in the fact that some advanced features (like inter-container communication) is tricky to get correct.