TrustRadius Insights for Docker are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Containerization: Multiple users have praised the efficiency of containerization, with some mentioning that it enables faster deployment pipelines and reduces the time required for deployments. Additionally, reviewers have found the container system to be well supported, allowing for seamless integration without complicated setup or user experience.
Improved Application Portability: Several reviewers have highlighted the portability of containers as a major advantage. They mentioned that containers are extremely portable, allowing for easy application portability across different environments. This feature enhances collaboration and scalability by enabling seamless sharing of container images on the cloud hub.
Smoother Collaboration and Integration: Users have appreciated how containers enable smoother collaboration between development and operations teams, facilitating the adoption of DevOps practices. Reviewers also mentioned that integrating containers with CI/CD pipelines is valuable, as it enables secure application development and efficient testing environments.
Docker helps us to run DBT in our local environment with help of Docker container and Docker image. Docker helps us to deploy our code with continuous integration and build highly scalable data processing system. The use case for Docker in our organization is to create a containerize data analytics and transformation pipeline. We use docker to containerize our DBT code.
Pros
Docker can deploy applications in different environment.
Docker is great for continuous integration and continuous delivery(CI/CD).
Docker provides fast and consistent delivery of our application.
Cons
Docker should provide integrated tools to troubleshoot issues in the containers.
Docker can improve their support and documentation for storage solutions.
Docker can improve their logging and monitoring tools to show deeper insights on container performance and health.
Likelihood to Recommend
Docker can be well suited for accelerating application development with the help of Docker containers. Docker can also be used when you have to deploy your code on multiple environments. Docker is very useful when you are creating mobile or web application running on server but for desktop application it may not be the best choice.
We're using docker for containerizing the micro services that are created in our organization. With this we're able to use machines and servers very efficiently and even deploying services got very easy for us. With docker it is very easy to deploy any application because most of the dependency are automatically managed by it.
Pros
Micro services containerizing
Automatically managing dependecny
Avoiding conflict between multiple application related to library and operating system
Cons
As of now it doesn't support legacy OS which they must support
Very resource consuming, can be improved
Likelihood to Recommend
If you have multiple application in same language like python then there are very high chances that you may have library conflicts and platform related conflicts that can be handled by it.
If you have multiple applications that needs to be deployed on same server then also it can be used.
If you have to deploy application in clusters then also it can be used.
Docker helps us with - Container system - Remember the good old days where we had different systems supporting different environments. And developing apps may lead to different bugs in different environments. With Docker this issue is gone. Same config and settings throughout devices and servers Easy site local setup, site deployments and multiple containers are also supported
Pros
Container system
Local site setup
Integration with CI/CD pipeline
Cons
While using Docker with lando, the latest versions are generally not supported
Docker is system heavy
Likelihood to Recommend
Docker is really well suited for version controlled site developments or maybe even normal site developments in general as they use container system. Adding that up with Kubernetes the advantages are tremendous and unavoidable if institutions are looking for hassle free development from their teams.
We have used Docker for creating images for our project and deploying that image using kubernates. It is very much useful for other developers as if we are creating images successfully then no one will face errors in their systems. We have added this phase in our Jenkins build so that this step will not be missed.
Pros
creating image for the project
help in deployment
help in maintaining identical environment in all the system
Cons
we can reduce the image bundle size
images should be killed automatically in idle state.
understanding docker desktop app is a bit tricky.
Likelihood to Recommend
It helps in deployment of the project. Sometime the size of the bundle is huge and there should be some way to reduce it. it helps in maintaining identical environment in all the developer's system. Without Docker, maintaining deployment build is very difficult.
Docker is used to build and deploy all our images. We also use Docker to host all our images in a registry which is used company wide to make it easy for different teams to pull down and push images.
Pros
Deployments
Containersation
Build images
Cons
User limit
Speed
Likelihood to Recommend
For large applications that are regularly updated via various teams. When you need a quick, easy and sufficient solution for your containerisation and deployments within your organisation. If you have a high number of team numbers, Docker does not work particularly well due to the limits placed on certain accounts. Users using VPN would have to wait until some free user space, in order to push/ pull images. I believe the Enterprise edition resolves this issue.
Docker is across our development department to provide an isolated environment to isolate and deploy web applications, mobile applications, and scripts.
Pros
Isolation
Security
Efficiency
Cons
UI
Documentation
Likelihood to Recommend
Docker is best suited when you have multiple versions of an application or when you have multiple client environments that you need to support. Docker won't help much when you have a single application that is supported in a single platform.
Docker is used in a multitude of ways at our company, it is used as our container service for our Kubernetes clusters. We also use it to run our applications on our bare metal servers. Furthermore, we use it to spin up resources for our ephemeral testing environment. Docker helps us worry less about the infrastructure we are deploying and more about the application. It also helps speed up deployments and developing pipelines as we have a solid design pattern around it.
Pros
virtualization
community support
build once deploy anywhere
Cons
container networking is obtuse
needs privileged access
incompatibility for periods for new processor architectures e.g. M1
Likelihood to Recommend
You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
Packaging of application to limit the space occupied
Ease of running the application
Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc
Cons
Handling the unused images
/var/lib/docker/overlav2 directory contain hash code instead of docker can provide some real name so that user can housekeep the containers, volumes etc
Logs of containers in the base machine after it exits
Likelihood to Recommend
We integrated our pipeline i.e. gitlab pipeline with docker to create images using docker files with all application and pre requisite inside the image. Once image is ready we have integrated it with terraform to create infrastructure on cloud and test it and then destroy the container and image so that space can be reused. After terraform creates the infra we jse ansible to login into the machine using roles i.e. ssh roles and configure the VM with required softwares. So docker helped us to build the initial infrastructure and then reuse it by claiming the space and it helped us to avoid buying more virtual machines.
Docker is used to build applications in a faster and efficient and reliable way. It is used across different teams and departments across the organisation. It solves one of the critical challenges in building IT solutions , "time to market". It helps teams in prototyping the solutions much faster and also makes sure there are no surprises at the higher environments like Staging or Production.
Pros
Build containers in a secure, reliable and faster way
Manager multiple versions of the containers and images efficiently
Manage the images on the cloud (hub) and share seamlessly
Deployment pipelines are efficient and less time consuming
Cons
Docker hub image retention policy can be relaxed
Docker hub policies can be more developer friendly
Docker CLI help section can be improved
Image and container storage (local) management can be optimized
Likelihood to Recommend
Docker is the market leader in Containerisation and its best used to build applications in a faster, efficient and reliable way. It helps teams in prototyping the solutions much faster. Containers can be shipped and shared across different teams, different environments and even for different platforms and applications. It is well suited for developing micro-service based applications and also state-less applications. Monoliths or state critical applications are less appropriate but can be developed provided "support systems" are available and a suitable architecture is designed.
VU
Verified User
Engineer in Information Technology (10,001+ employees)
It is used across our organization as our AWS stacks depend on it for Docker images usage across AWS accounts. [The] deployment of our product service stacks depends on Docker to host the docker images for our product microservices containers for updates, etc. Docker Desktop is where we use to switch context for different account images.
Pros
Kubernetes context switching - very handy
Integrate well and seamless - No complicated setup and or UX
Ease of updating images and etc - very important
Cons
Docker Desktop, despite setting resource preferences, can cause CPU spikes for long after work is done
Likelihood to Recommend
Docker is well suited for what it does best - container images administration, management, and deployment. Updates is easy, seamless, and integrate well with Kubernetes and whether your deployment is metal/cloud, it works well. CLI is great, and I have not used any other tool to manage. Docker Desktop is simple. It does what it does it says on the can; however it eats CPUs for breakfast, lunch, and dinner - all the time even on recommended resources and all Docker's work is already over and done. It's a known issue on Mac and Windows. So there is room for improvement.
VU
Verified User
Engineer in Product Management (201-500 employees)