All our web applications use Docker for testing purporses and production enviroments and is a must inside our organization.

I think every software corporation needs to migrate their server architerture to contenerized enviroments and Docker make it easy to maintain and scale all web applications because you can have all your services or microservices running isolated and that gives you the possibility to have multiple softwares developed in different languages for every service that your application needs, for example: You can have a running container with Apache Server for your backend using PHP, and another NodeJS container for your frontend, a MySQL database service for your data and a Redis service for the cache management all in the same network sharing for every project or even for different projects in another networks, possibilities are unlimited.

In my oppion, there's no cons using Docker, I think you'll get more gains rather than pains in your software business.

Feels like a bit of a learning curve coming from using VirtualBox, vagrant, etc., but when you get that first cluster of virtual environments running interacting apps you know how worth it it was

Docker works on every platform and makes it simple to match production and development systems. It's similar to older virtual machine and VM management tooling, but much more lean and 100% open source.

Getting started can be intimidating. While it's worth the time invested, development teams accustomed to working directly on their own hardware or with traditional virtual machine tools will have a bit of a learning curve.

We are running a fleet of microservices on Amazon ECS and Docker is part of our development, testing, staging and production environments.

It's become a de-facto standard and there are a lot of resources online to learn everything, from basics to the really advanced tidbits.

Being a very complex system, sometimes it's hard to keep track of all the parts. Is runc part of Docker? What about containerd? What's moby? The fact that operating system packages with the same name include different things doesn't help. Sometimes there are also subtle bugs that take days to track and attribute to Docker.

I think it's an industry standard right now and it works well

It is a tool that requires a good knowledge to really know how it works, it is not accessible to everyone and it is not very user friendly.

It allows you to create isolated and lightweight development environments. It allows reducing errors in production deployment by avoiding dependency on the environment. It facilitates devops tasks and in combination with other tools, facilitates monitoring and scalability.

It is a difficult tool for newbies to use and is difficult to secure. Also, images take up a lot of space.

Very powerful; extremely flexible; huge community support; vast integrations with other products/technologies

Steep learning curve when moving to Docker (or containerization in general) for the first time.

The best feature I like about docker is that I can encapsulate work in a container and deploy it anywhere like Azure Container Instances, Amazon EKS, Digital Ocean or even my desktop. I like to create containers with python + security tools like SSL Scanners and deploy them near the servers to test and outside the servers to test to have an accurate picture of what's supported. It also helps with powershell core since you can create docker container with specific modules and give them to co-workers so they don't have to install the modules on their PCs. I also like integrations like Trivy that come built-in to docker desktop so you can scan the images for vulnerabilities and also like Slim.AI to make images smaller.

The recent licensing changes made me discover Podman and switched a few workloads already.

In programming, we sometimes perform the same tasks over and over again. Docker allows us to have ready-made repositories of functions, codes and even robust tasks that we can use in different projects without having to create them again from scratch and better eliminate the likelihood of human error. . I really like it because it's free for the local environment and because it's open source.

One of the things that worries me is that Docker is not very friendly to consuming virtual machines, containers consume considerable resources. Difficult to manage in complex projects where we have several connections and layers. Monitoring should be improved.

We solved a monolithic structure implementing Docker, it was a hard process and it's not really easy, but if it's well done you can rest assured that you will have much fewer problems in the future. Capacity and maintainability skyrocketed after we started using it, so we have much to thank Docker.

I think the most impactful and beneficial thing about Docker is the capacity to hold an entire program with an insanely low size (30MB for an entire and fully operational Alpine-linux!!). This enables a world of microservices to be created and never depend on one thing, you can have 6 different micro services hosted on 6 different containers and each and every one can be resetted without holding the rest hostage.

I think the implementation process could be easier, sometimes you really need an easy-access terminal and Docker is not that friendly when it comes to that, I have high hopes that they can resolve that issue, for example as Anaconda did, a separate executable terminal for each virtual environment, this could be a separate command terminal for each container.

Even if the image creation may be a complex issue, the rewards makes it worthwhile. And most of the time I can pull the image I need from a repository so I don't have to create it from scratch

It allows me to install software that otherwise the installation procedure would be too complex. I also use it to provide isolation between different software, like using different Python versions.

I don't like the procedure to create a new image, sometimes is complex. Security is also not easy to manage, since in most docker images lot of tools are disabled by default so it is hard to make updates, you have to update the base image.

We have solved the stability issues with using distributed Docker containers. Our downtime on our website significantly dropped down. I can tell that my overall experience with Docker is very good.

It has great community online. When I need help with some configuration or error, I can easily find the solution. Also the Docker containers are very stable and fast. It can easily be deployed using a regular CI/CD tool.

Nowadays, using standalone docker containers are not a common way. You need to use Docker with Kubernetes. I'd be glad if some developments will be performed for the aim of using Docker standalone containers.

I have been using Docker for a few months now, and overall, I have had a positive experience with the tool.One of the things that I like most about Docker is its portability. Containers are lightweight and portable, which makes it easy to deploy applications on different environments and platforms. This has been particularly useful for me, as I often work with a variety of different systems and environments.I have also found Docker to be very helpful for ensuring consistency across environments. By packaging up all of the necessary code, libraries, and dependencies in a single container, Docker helps to ensure that my applications will run the same way regardless of the environment in which they are deployed.In addition to its portability and consistency, I have also found Docker to be very scalable. It is easy to create and deploy new containers as needed, which makes it straightforward to scale applications up or down as needed.Overall, I have had a positive experience with Docker and would definitely recommend it to others. It is a useful tool that can help to streamline the development and deployment process, making it easier to build and manage applications.

- Portability: Docker containers are lightweight and portable, making it easy to deploy applications on different environments and platforms.- Consistency: Docker helps to ensure consistency across environments by packaging up all of the necessary code, libraries, and dependencies in a single container.-Scalability: Docker makes it easy to scale applications by allowing you to quickly create and deploy new containers as needed.- Ease of use: Docker provides an intuitive and user-friendly interface for managing containers and images.

-Security:Docker containers can potentially introduce security vulnerabilities if they are not properly configured and maintained.-Resource utilization:Docker containers can consume resources such as CPU and memory, which may impact the performance of other applications running on the same host.-Complexity: Using Docker may add an additional layer of complexity to the application development and deployment process.

Docker images may be created relatively easily, and distributing them is even easier. We can easily containerize and host our lengthy code, which allows us to work quickly on production. With Docker, we can serve users anything or everything that is hosted as a service.

I can state with certainty that it has helped me avoid a lot of time-consuming problems with software deployment. Our large project can be divided into smaller components, which we will then deploy in containers to enable independence. We can provide the appropriate environment needed to run our project using a Docker Image file. Applications can be set up and executed more quickly with the help of a large selection of pre-built containers.

Images can occasionally be quite huge, and Docker can use quite a lot of CPU and memory on a computer. On systems with little setup, it ages. For it to function effectively, a decent system is needed. The performance of Docker Desktop might be enhanced.

Overall Docker allows me to quickly setup applications locally and do quick tests, then tear down these environments.

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.

Docker has given us a reliable way to reproduce development environments across multiple work machines as well as on production environments. It's sped up our process of getting new developers setup on projects as well as starting new projects knowing that they'll just work. It's been a great boost in our efficiency to take on new projects.

Docker is great for setting up development environments for projects and making sure everyone is working on the same basis. That includes locally as well as in production environments. Once you have you have your configurations set it becomes trivial to drop it into any project with similar requirements. It's very flexible in what it allows you to do. It definitely speeds up the on-boarding of new team members.

Docker works 99% of the time. It's fairly reliable. Every now and then things won't work for no reason. It usually ends up being some or other obscure issue. Luckily enough if you search hard enough there's usually someone that has experienced the same problem and has managed to resolve it. There's thankfully many ways to tackle a problem when it comes to Docker.

Docker allowed us to containerize and deploy our large application. By packaging environment configuration with the application code, we were able to continue running applications which required outdated versions like Python 2, even though the server environments didn't support them. It also allowed our distributed team to work on Linux servers and Windows machines, on the same codebase, without having to fight over dependency mismatches

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 Enterprise is a leading container platform because of the feature and customization provided by it. We are deploying the multiple client server without any major effort. Docker helps to deliver the release of the product with better compliance. High level encryption of images and communication between cluster make the container secure.

Docker is a powerful tool for containerization. It gives the platform for build, test and deploy application using container. The Docker container helps in adopting the DevOps methodology that helps in rapid release. Docker container helps to isolate the application which helps to execute the consistent test results. Dockers helps to optimize the development and operational process. Docker Enterprise provides a one stop solution to all problems from its dashboard.

Docker daemon configuration for container and images is a tricky part and it should be simplified. Managing the Swarm and Kubernetes for orchestration is a complex part with using Docker API.

Time saving, money saving, two great benefits !

The community is highly reactive, the software is stable, can be easily used, even if your are not a technical guru. Docker simplify usage of tools, apps. No more worries about which version of this lib, or this framework to install and run an app. It is easier to try things too, you get the container, you run it, and you test, no more complicated install, no more OS breakage because you have to install some new version of a lib who break the rest of your setup ! Last but not least, it's simple to deploy and use with some majors cloud hosting, it is a great tool for starting businesses, and you have can scale if you need to, start small and save money, and if you need, go big.

You have to choose or manage well your container, the main trouble to my point of view is to have too old container, meaning you need to update your operating system to have the more recent security feature, if you have an old operating system you are vulnerable. People often don't think about that aspect, and the risk is to have lot of apps running on old OS.

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.

Mainly we use it for managing our application instances (multiple instances of same application for many users)

Configurability and the basic setup is quite straight forward - you can basically get something up and running within few hours. This gives you infinite possibilities in extensibility and the manageability - but with some limitations that can be addressed with some third part applications.

Steep learning curve involved as well as lack of in-built monitoring an recovery tools. You have to depend on lot of "third-party" application to make this a production ready system.

With proper setup it can make managing web applications a lot more effective. (it's good for more than just web applications, but that's what I use it for). Being able to quickly spinup or restart docker containers has a lot of advantages for fixing issues or working on development.

If you're using docker in a development environment on your computer it can get very resource intensive really fast depending on how many containers you're needing to run at a given time. For just a few containers with small images it's not too bad, but I have several containers all needing to be ran at the same time and sometimes my computer fan just won't stop. This is less a concern when being run from a webserver where you can increase resources to meet demand.

Docker has an extremely adaptable work process in which I work with in situations and in addition portable applications to website pages, it fills in as a virtual machine to copy and recreate its functionalities.

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.

Since I started using docker, I no longer needed to use other tools for managing and creating environments.

on macOS, with some projects there is some slowdown but I also know that a problem with the platform and not with the docker itself.

* Before docker, we have to provide the Virtual machine and also make the configurations on the virtual machine but after Docker we do not have to setup those configurations as give the container and make it work .

* A container based application which eases to make deployment and execution of your program. You do not have to say customer download those and make those configuration at those files. just give the container and he will have the all the application with the working environment in it . I guess it's one of the best invention at this century.

* PErsistent data storage is not simple at it's described * Unfortunately not all the applications support containers * It does not work with well if your application have lots of graphical features