Docker Reviews

The solution is used to run systems in small applications.

You should start by running your applications to ensure optimal performance in a Docker environment. The administrator should validate the setup with Kubernetes before deployment. This process includes validating our software applications and comparing features with other open-source alternatives. It’s important to understand that application performance can vary due to various factors. For instance, issues may arise due to ZDR policies. Before deploying in production, consider using OpenShift if additional features are needed. Our organization currently uses Oracle, but Docker provides a flexible and efficient way to manage our applications.

We use Docker to facilitate deployment, updates, and management.

Enhancing artificial intelligence capabilities and cluster management should be a priority. It should facilitate some security management.

I have been using Docker for four years.

I have been going through the session block for enhancement. I rate the solution’s scalability a six out of ten.

The initial setup is straightforward.

It requires a premium subscription.

The CI/CD was created, and the template is there. It's sufficient to prevent blockers. The restore is deployed, and we are conducting large-scale scans to identify duplicates. For continuous intelligence, we are using Azure DevOps tools from GitLab. We use Docker for various tasks like scanning, automation, testing, and searching.

We support software implementation and maintenance. Nowadays, we update our software regularly. Our recommendation for regular users is to avoid using outdated software, especially when it involves personal data sources such as software applications, desktops, and internet usage.

Azure uses Docker and integrates with Azure products. Docker overlaps the network, which facilitates communication between containers. This network operates on VPNs but can utilize third-party gateways to reach and solve problems.

Docker has more advanced authentication, backup, and accountability.

Overall, I rate the solution a six out of ten.

I use the solution in my company for internal applications and deployments in the DevOps area. The tool's main use cases revolve around areas like research and development tools and CI/CD pipelines.

The most valuable features of the solution are the support I get from Windows and Linux, along with the cloud platforms and the CLI. There is also a repo feature in the tool.

The backup compatibility for legacy window stations is an area of concern where improvement is required, especially since my company has certain legacy tools that we are struggling to move. In our company, we are still unable to move certain things to Docker.

Docker should do something the same way GitHub has added AI and Aline, which can basically do a lot of work for users.

I have experience with Docker.

It is a very stable solution. Stability-wise, I rate the solution a ten out of ten.

There are no scalability issues with the product.

There are no challenges in scaling up the product for larger applications.

I work in a big company, and I only know that my team uses the product, but I guess there might be a lot of people who use it in our organization.

The product's initial setup phase is straightforward.

The product's deployment phase was easy as we had to just install it in our company.

Two engineers are required for the deployment and maintenance of the product.

The solution can be deployed by me in our company.

The product has helped with the cost-savings part, especially since our company operates in a repeatable environment where it is easy to deploy the tool for multiple users.

Though I don't know about the payments associated with Docker, I know that it is done centrally by your company.

My company considered a product named Automaton against Docker. My company did not like Automaton. Docker is more commonly available and well-documented, and it is easier to get a lot of information about it on the internet.

In terms of the impact of container orchestration, I would say that though my company does not currently use a lot of containers, we plan to move to containers.

I recommend others to just use the internet than ChatGPT since mostly all issues are already known and very easy to deal with so it is better to use the knowledge from the industry.

In terms of the use of Docker for AI projects or workflows, I would say that my company deploys AI applications on Docker, like any other application and pipeline.

The tools or practices that have proven to be the most beneficial for our company's AI initiatives are agnostic to Docker. There is nothing special in Docker, and our company just uses it to deploy applications.

The value derived from the use of the product revolves around the scalability and the reliability it offers. The product helps with the cost-savings part since it saves time and money linked with the amount of engineers required to spend time on operations.

I rate the solution a nine out of ten.

Docker helps us implement applications quickly.

Docker is convenient and easy to use. We can create and implement different types of virtual machines. It provides a lot of flexibility. The applications can be deployed quickly.

The stability could be improved.

The product is stable and reliable. I rate the stability a nine out of ten.

Five engineers in the IT team use the product in our organization.

The support team is fast, customer-friendly, knowledgeable, and quite professional.

We didn't face any issues with the installation.

We deployed the tool in-house.

The tool provides a return on investment. We are able to deploy some services and applications faster and be aligned with business requirements.

We have a monthly subscription. The product is not expensive. I rate the pricing an eight out of ten.

We do not use the solution often. It works well. We don’t have huge projects. I will recommend the tool to others. Everyone in IT uses Docker. Everyone knows it. At some level, a company must find a way to use Infrastructure as a Service by implementing different container technologies like Docker. Many IT personnel are aware of the solution. Overall, I rate the tool a nine out of ten.

I use Docker for containerization, deployment, and to create packages. Docker has a wide range of uses and integrates well with other command-line tools like Terraform. Docker is most helpful when trying to work with CI/CD pipelines.

Docker's containerization property is its main selling point.

I'd like to see the new update on containers and what you can achieve with the new version of Docker by using containers. I would also like to know the range of applications for which it can be used. I want to see if new architectures have been incorporated in Docker or if we have to wait for another release.

I have been using Docker for one year.

I rate Docker a nine out of ten for stability.

Docker is a very scalable solution. I rate Docker a nine out of ten for scalability.

Docker's initial setup is straightforward. As a command line tool, it also provides you with docks to reference if you get stuck or have issues.

The solution's deployment time depends on your internet latency or internet speed and the size of the container. If you are deploying a very large application, it will take some time to set up.

Docker is deployed on-cloud in our organization.

To effectively use Docker, users should learn the basics of Docker and understand what containers and images are in Docker.

Overall, I rate Docker a nine out of ten.

I use the tool for SQL, MySQL, and web development.

I think that with Docker, it is easy to deploy it on different platforms.

Stability is an area with a shortcoming. Hence, stability needs to be improved.

I have been using Docker for a year. Also, I don't remember the version of the solution I am using since it comes from the repository of Linux.

I rate the stability of the solution a nine out of ten.

Normally, I use it on small sites, so I don't know if it can experience scalability.

More than 200 of my students use the tool. Also, the tool is used extensively by me.

Normally, Docker is free for everything, so I don't know if there needs to be a plan to increase the number of users.

Before Docker, I used only a Linux setup.

I have used Docker on Linux for the filesystem.

The deployment of the product was done in a minute or two, considering my internet is very stable.

I use the Docker control plane for the deployment.

I was involved in the deployment process of the solution.

Docker is a free tool.

I would definitely recommend the solution to those planning to use it.

I don't know what to say to those planning to use Docker, but you can find its details on the internet.

I rate the overall solution a nine out of ten.

We use the solution for containerization. We've replaced it with other solutions. We are using it to compartmentalize some legacy products. We are also onboarding other third-party applications using it. We have a few use cases. 

It's helped to save many resources.

The features, such as scaling and high availability, have been excellent. 

It is easy to set up. 

The solution is stable.

It can scale well. 

The pricing could be a bit better. We'd like the least amount of spend as possible.

We'd like knowledge transfer to be easier.

The support could be better. 

The solution can be a bit expensive. 

I've been using the solution for about six years so far. 

The solution has been pretty stable. 

The solution can scale well. 

I'm not sure how many users are currently using the solution. We are migrating all development teams over to containers. 

We have support from our vendor and also use support for the Kubernetes cluster. It could use some improvement. It could be a bit better. They should be more responsive. 

I've been working with Kubernetes alongside other solutions. 

The implementation, for me, was pretty simple. I'm not sure if others would have issues. 

I would deeply it on top of the Kubernetes cluster. It usually takes one day to deploy. We're using Docker as a service for testing purposes and have implemented it on Kubernetes clusters in order to test and deploy applications in order to handle production-grade applications. 

Have not looked into ROI to see if we have witnessed any. 

I'm not sure what the exact pricing is. I don't deal with licensing. However, my understanding is it is expensive. 

I started using the trial version and moved on to the latest version. 

I'd recommend the solution to others. I'd rate it nine out of ten. 

We used to have a silo problem. Docker solved it because we're able to containerize the microservices that we're developing in the form of Docker mail.

Once we run the Docker image, it becomes a container. This container is guaranteed to run in every machine because we're installing Docker as the platform. On top of Docker platform, we're curating the Docker images and running the container. That container has a limited number of libraries and a limited number of data, which is required to run the application.

Each container has a limited library system, which is required to run the application. This encapsulation makes it work perfectly, irrespective of the system. It works perfectly once we have encapsulated the application and containerized it. This is guaranteed to run in each machine.

We're deploying the solution on Azure cloud. We're curating the CI/CD pipeline. In the CI/CD pipeline, we're curating the Docker images and pushing it to the container registry. We're writing the steps for how to build the Docker image into the YAML code. Once the Docker image is built, it's pushed to the container registry. We're writing this YAML code in the pipeline.

Every person on the DevOps team is using this Docker tool.

We have plans to increase usage because it's a great tool, and it's the latest technology. We're no longer developing monolith architecture, so everyone is developing applications with microservices. Docker is the best tool to containerize the application and encapsulate it.

We used to work on monolithic architecture to develop the application until it goes to the production environment. It takes a huge amount of time. Now, we are using a microservices architecture. Rather than creating the application as a whole, we are dividing the application into small services. Each microservice is loosely coupled. With each microservice, we can develop and containerize it in the form of a Docker container.

If an application has a hundred microservices, like on an e-commerce portal website, then the login is usually one application, the catalog is one application, and the E-card is one application. Each application can be considered as one service. For each microservice, we can develop a code and containerize it.

Containerization is the most valuable feature. I can communicate to the Docker containers using other containers. The copying feature is helpful because if a container dies, we won't lose the data. That data is retained because of this data volume feature. We mount it to our shared system or any shared folder.

I would like to see a more UI-based tool so that students can easily understand it rather than memorizing all of the Docker commands. Some people try using Docker desktop and containers to make it graphical.

Docker Swarm could have more advanced features, like Kubernetes, which has an auto scaling feature and cell-filling capabilities.

I have used Docker for four years.

I would rate the stability as seven out of ten.

I would rate the scalability as seven out of ten.

I would rate technical support as seven out of ten.

Setup is simple. We can install Docker with just one command. It doesn't take more than three to four minutes to run the pipeline. A Docker image is built in that time frame.

We're running the pipeline in a self-hosted agent or Microsoft-hosted agent.

Docker Compose can be installed easily. It allows you to use multiple containers at a time. Docker Swarm can also be installed easily.

Docker is open source. To use a Docker enterprise model, we would need to pay for it.

I would rate this solution as seven out of ten.

My advice is to create an account on Docker Hub. In Docker Hub, there are three Docker images available for practice. We use GitHub to see how we're making the Docker images and then push it to the public Docker Hub. I have an account in Docker Hub and have images there that I can reuse later. I would also advise completing a Udemy course for Docker or watching YouTube videos about it. This will make Docker easier to understand.

Docker can be deployed on-premise or on the cloud.

We are using Docker for containerizing our applications.

The most valuable feature of Docker is that it provides a containerized environment. The isolation between the environments is beneficial. Additionally, the solution is easy to use.

Docker can improve the integration with Microsoft Windows. It does not support native installations. 

There can be a lot of issues with Microsoft Windows and Docker and those issues should be resolved in a future release. For example, if you are running Docker and you are running a lot of things in Microsoft Windows, these issues should be resolved.

I have been using Docker for approximately 

Docker is highly stable.

The scalability of Docker is very good.

Every machine learning group in my company uses Docker. We have approximately 2000 to 3000 people using it.

I have not needed to use the support from Docker because I have not had any issues.

The initial setup of Docker was extremely easy. The only part that takes some time is the containerization, the rest of the process is quick.

I rate the initial setup of Docker a ten out of ten.

Docker is a free-to-use solution. However, Docker Enterprise is not free.

We chose Docker over other solutions because it has a relatively large use user base. It is a popular solution.

If you are trying to use Docker for the first time, make sure that the Docker file you have or the containerization which is done, is done properly. If the containerization is not done properly there can be some folders that are not mounted correctly and it causes several issues.

Docker Enterprise takes less time to set up if I was to compare it to this Docker free open-sourced version.

I rate Docker a nine out of ten.

We use this solution for our web applications and websites for automatic deployment. We also have a cloud based solution that we sell as a product and we offer cloud hosting, which is Docker based. Our clients have access to a graphic user interface where they can deploy their websites with one click and we use Docker in the back end to make that possible. 

Docker is an entirely containerized cloud solution that supports different types of applications running on the cloud including websites, web applications, APIs and some Lambda functions. We have a whole bunch of stuff running on the cloud. We have thousands of users supported by this solution. 

There are ways of using Docker where you have absolutely no dependencies on the environment that you work in. This allows us to deploy Docker anywhere anytime and this has been most valuable.

Docker removes any dependancies when it comes to deployment. We can ship it between different devices and different locations without our clients being impacted or aware. In once instance, we redeployed a client's container without losing any of their data. 

There are elements of stability that are problematic. One of the most recent upgrades created a major incident on our cloud, whereby the containers were not restarting automatically. Docker is a fairly new application and has matured and improved since 2016 but still needs improvement on stability. 

Prior to using Docker, we used a CH root and jailing process. Essentially, Docker is a CH root on steroids combined with an image management system that is based out of git code. When you're dealing with such low level technology, there should not be issues with stability. 

We have been using this solution since 2016. 

This is a scalable solution

The setup on the most recent versions of Windows is pretty straightforward. The setup on Mac is also pretty straightforward, but there are networking problems.  Docker, it doesn't play well with the Mac virtual hypervisor. There are some issues on that side. On Linux, well, it's less straightforward, you have to know how to work it out. There are no performance or networking issues.

We have done in house deployments and we have also used other tools like Kubernetes or Docker Compose. We have our own PHP library that can deploy Docker containers, which is called Linux for Composer. It is oriented towards helping PHP developers to use Docker to make things more simple. 

We have definitely experienced ROI because it cuts down on development time. There are no surprises when it comes to deployment. It cuts down on development, deployment and it cuts down on staff. There are multiple advantages including on the financial side.

We've had a look at other possible solutions such as KVM and Pod Man. Pod Man is not very mature right now. There are a lot of things that we're used to being able to do with Docker that we can't do right now with Pod Man.

We're not excluding the possibility of using Pod Man. There is also an equivalent to Docker which is the Windows subsystem for Linux, WSL two. We've used that for a few projects in Windows environments, and we are considering putting our Linux distribution on WSL two.

I would advise others not to use Docker as a virtual machine or to think of it as being similar to VMware or Virtual Box. It has an entirely different use case. They have to think about it as a system that is used on an ad hoc basis. 

If you build thinking that it is temporary in nature, you will have the full benefits of Docker. 

I would rate this solution a nine out of ten. 

I use Docker to create dev stacks, usually for developers to plug and play their applications, and in cases where they don't need to be bothered with complex architectures and decoupling services. We create a simple Docker compose file and provision it. We are customers of Docker and I'm a DevOps engineer.

The lift and shift is valuable because you create a lightweight image that can be accessed by anyone who has installed Docker.

I'd like to see improvement in some of the documentation because there are currently errors and it requires a thorough check and deep dive to make sure it's correct. If they were to incorporate what the community offers into the documentation, it would be beneficial.

Many people use multiple containers for their workload and it would be great to have pre-deployed solutions for typical deployments like WordPress and multiple CMS which would encourage more developers to use Docker. I would love to see the solution with pre-baked, ready-to-go capabilities for multi-container solutions.

I've been using this solution for five years. 

I haven't found such complex issues that I need to contact customer support. I found most of the answers through the community or using a work around. 

The initial setup is very easy. You just need some basic understanding of the system, and how containerization works. Images are already prepared so if the user doesn't have the images on his local system, Docker pulls it from the repository and it's good to go. It's much faster if the images are downloaded. As a DevOps engineer, I generally carry out the deployment myself. 

I recommend learning about containerization prior to using this solution starting with basic deployments. Take the opportunity to test it out and check the components. Docker has relieved a lot of the pressure, including the fact that I no longer have to provide everything from scratch. I know I just have to install the Docker community edition, make Docker images and get going. That said, Docker has some limitations and Kubernetes has discontinued using it. It's compatibility is reduced as a result and many organizations are moving towards Kubernetes and other orchestration services.

I rate this solution seven out of 10.