Docker hub Reviews & Product Details

For microservices this is one of the best platform to run the applications and here containers gets start in seconds and seamlessly we can scale up as we need and scale down as well these are very lighter than the Virtual machines also faster deployments. Review collected by and hosted on G2.com.

Initial setup is bit tricky and requires some good knowledge on it and likewise how we directly get into linux machine and troubleshoot kind of things wont work here and managing more dockers also is bit tedious one also internal network and security is always hard to understand. Review collected by and hosted on G2.com.

Honestly, what I love most about Docker is how it completely eliminates the “works on my machine” problem. Since I started using it about a year and a half ago for both local development and production deployments, my workflow has become far more predictable and consistent across environments.

Being able to spin up isolated containers for different microservices is a real game-changer. I can run the entire stack locally without dependency conflicts, and deploying to production feels much less stressful because the environment is essentially the same as what I tested on my machine.

One unexpected benefit I didn’t anticipate is how much faster onboarding new team members has become. Instead of spending half a day setting up a development environment, someone new can just pull the image and be up and running within minutes. That alone has saved us countless hours. Review collected by and hosted on G2.com.

There are a few friction points worth calling out, although none of them are dealbreakers for me.

On the UI/UX side, Docker Desktop can feel sluggish on lower-spec machines. The interface has improved a lot overall, but some advanced configurations still end up pushing you back to the CLI or into manual file editing. I’d really appreciate a more guided experience for those scenarios.

Performance on macOS, in particular, can be frustrating. File system sharing between the host and containers introduces noticeable I/O overhead, especially on larger projects, and that’s something I run into regularly during local development.

When it comes to integrations, most of them work well, but setup can get complex quickly when you’re orchestrating multiple services with specific networking needs. It isn’t always beginner-friendly, and some third-party integrations require more configuration than you’d expect.

Pricing/ROI became a sore spot when Docker introduced mandatory paid plans for larger teams. It felt abrupt, and some smaller teams I know had to rethink their tooling because of it.

Support and onboarding are generally solid, but official support response times for paid plans can be inconsistent. For more complex issues, I often find myself relying on community forums rather than getting direct help.

As for AI/intelligence features, they still feel fairly early-stage. The suggestions and scanning tools are useful, but they aren’t deep or customizable enough yet to feel truly intelligent—more of a nice extra than a core strength. Review collected by and hosted on G2.com.

What stands out most about Docker is that it makes apps run the same everywhere. It’s easy to set up, share, and deploy without worrying about differences between machines. The UI and UX are simple, with clear commands and tools that are easy to learn. It integrates well with many tools and cloud services, runs efficiently with lightweight containers, and helps reduce costs by improving resource usage. Review collected by and hosted on G2.com.

One downside of Docker is that it can be complex at the beginning, especially when dealing with networking, volumes, or orchestration. Review collected by and hosted on G2.com.

The biggest advantage for our engineering team is how Docker handles complex, multi-language local environments. We have a core monolithic application built on PHP and MySQL, but we also run separate microservices built with Python and Flask for specific background tasks like image processing. Before Docker, we had to rely on heavy, cumbersome virtual machines to keep everything isolated, and configuring Nginx, PHP-FPM, and Python dependencies on every developer's machine was a nightmare. Now, we use a single docker-compose.yml file. With a quick docker-compose up -d, I can spin up the database, the PHP backend, and the Python microservice in isolated, identical containers within minutes. Review collected by and hosted on G2.com.

The resource drain is the biggest pain point. Running Docker Desktop on Windows or macOS consumes a massive amount of RAM. If I have my IDE open, a few browser tabs for research, and my container stack running, my machine's memory is easily maxed out and the fans start screaming. Also, dealing with volume mounting can occasionally be frustrating. We still sometimes run into weird file permission issues between the host OS and the Linux containers, particularly when scripts try to write to local log directories, requiring manual chmod fixes. Review collected by and hosted on G2.com.

I use Docker to containerize my projects, which ensures they run the same way everywhere. It's great because it helps me avoid installing all the necessary dependencies when creating a new environment or running tests. It makes the testing process much easier since it runs the same way it would on a developer's PC. I find it easier to rebuild my instances along with images as long as I'm familiar with the commands. This has been especially helpful for my Discord bot. Docker allows me to build containers, run them, and understand where my application is failing much earlier. The initial setup was very easy with no issues whatsoever. Review collected by and hosted on G2.com.

I faced issues while logging in the beginning and understanding what volumes are also takes a little bit of knowledge beforehand. Without that, you might struggle a bit in the beginning. A simpler explanation in the docs is all I could ask for. Review collected by and hosted on G2.com.

I use Docker to keep my development environment consistent across different systems, which really helps in creating and running applications in containers. I mainly use it for backend services, databases, and testing setups, allowing me to quickly start or stop projects without worrying about configuration issues. Docker solves the problem of 'it works on my machine' by making environments consistent everywhere, helping me avoid setup issues and dependency conflicts. I like how easy Docker makes it to run and manage applications. It saves time, keeps everything organized, and works the same on any system. Using Docker with tools like Kubernetes, Git, and CI/CD pipelines helps me manage deployments, version control, and automate builds easily. We switched from manual setup and local environments to Docker, which made our workflow more consistent and easier to manage. Review collected by and hosted on G2.com.

Sometimes Docker can be a bit complex to understand at the beginning. It also uses a lot of system resources, and debugging issues inside containers can be a bit tricky. Review collected by and hosted on G2.com.

What I like best about Docker is how easily it lets me run applications in containers without worrying about environment setup. Docker Desktop makes it simple to build, manage, and monitor containers from one place.

The most helpful part is consistency - apps run the same on any system, which saves time and avoids setup issues. Review collected by and hosted on G2.com.

One thing I dislike about Docker is that it can be resource-intensive, especially Docker Desktop, which sometimes uses a lot of CPU and memory. It can also be confusing for beginners to understand concepts like networking, volumes, and container management at first. Improving performance and simplifying the learning curve would make it better. Review collected by and hosted on G2.com.

I use Docker to run my applications easily. It helps me package my app with everything it needs, so it works the same on any system.

It also lets us create images of our applications, and it’s easy to share them with anyone. Recently, Docker integrated Kubernetes too, and now CI/CD has become easier. Docker Hub (or registry) contains a huge number of images, so we can use almost anything with just a command. Overall, both the CLI and GUI make Docker easy to use. Review collected by and hosted on G2.com.

Docker can be hard to understand at the beginning. Some concepts, like networking and volumes, can feel confusing at first. But once I understood them better, I realized they’re genuinely innovative features. Review collected by and hosted on G2.com.

The best thing what i like about the docker is agent-ready infrastructure basically these will provide isolated and secure environments specifically for ai agent to write and test the code without any risk to host in our machine.one more feature what i liked it will allow the user to describe entire service room in single file. for the new user it easy to use and if we are facing any issue related to this tool we have 24/7 customer support and even integration is too easy to connect with your backend application to create the image. Review collected by and hosted on G2.com.

what i dislike about the docker it will take more time to troubleshoot the dns part and host machine to find the actual problem from where it is occuring. Review collected by and hosted on G2.com.

I like best about Docker is how it makes application deployment simple and consistent across different environments. I can run the same application on my local system, testing environment, or cloud without worrying about dependency or configuration issues. Docker containers are lightweight and fast, which saves time during development and testing. Overall, Docker improves productivity and makes application management much more efficient. Review collected by and hosted on G2.com.

One thing I dislike about Docker is that it has a learning curve for beginners, especially when understanding Dockerfiles, networking, and volumes. Debugging issues inside containers can sometimes be difficult compared to traditional setups. Managing containers at a large scale also requires additional tools and knowledge. These challenges can make Docker feel complex for new users at the start. Review collected by and hosted on G2.com.