Docker on CentOS Reviews

I have been working as a senior middleware engineer and DevOps engineer for the last 17 years, where I have used Docker on CentOS in various multi-level, multi-cloud platforms like AWS and Azure, and for Fortune 500 companies such as Charter, Mastercard, Cardinal Health, and Dell. Currently, I'm involved in the containerization of Spring 3.x, Java-based applications, and building microservices for distributed applications using Docker on CentOS. The containerization we are doing was initially using ECR, which has now migrated to EKS, and I am creating the CI/CD pipeline with GitLab, Docker builds and Argo CD deployments. Our architecture includes an 80-plus pods cluster, scaling from 2 to 85, with a target of zero downtime and 140 TPS. Docker on CentOS, being lightweight and stable, integrates well with the Linux kernel, providing minimum overhead and cost efficiency, which is crucial for resource-constrained environments.

The capabilities of Docker on CentOS that I have found the most valuable include its use for Spring-based applications, which significantly enhance the value I derive from it. Docker on CentOS is particularly effective for building distributed applications and microservices. Deployments are smooth and easy, and the integration with Kubernetes is seamless. I have successfully managed 80-plus pods clusters, scaling from 80 to 85 with 140 TPS without encountering any issues. Docker on CentOS's lightweight nature allows for flawless development across environments such as dev, stage, and prod.

From my perspective, the experience with the deployment of Docker on CentOS is quite positive, especially for the CI/CD pipeline. The architecture overview includes the use of a Git repository and GitLab CI, which facilitates the Docker build for our Spring 3.x Java applications.

I have faced challenges with the end-of-life cycle of CentOS since 2021-2022, security updates, network complexity with multi-node DNS issues, storage persistence pain points with EBS and EFS, and resource management before the Kubernetes abstraction.

I have been working with Docker on CentOS for a very long time, starting with Docker Swarm and Docker, specifically for this current project itself.

While the end-of-life for CentOS was noted, the overall persistence and network performance, including firewall functionality, were commendable. Earlier issues with out-of-memory crashes were resolved with proper sizing adjustments, and overall, I experienced no conflicts during updates, maintaining the 140 TPS targets effectively.

Regarding the scalability of Docker on CentOS, I initially built the Docker containers and moved them to Kubernetes, where my scaling efforts were focused.

Once Docker on CentOS is dockerized and deployed in Kubernetes, it scales effectively by meeting the target of 140 TPS with an SLA of one second for three REST endpoints.

I do not often communicate with the technical support of Docker on CentOS, as I haven't found the need; the documentation has been sufficient.

The documentation for Docker on CentOS is excellent; I find answers to my questions regarding the Docker daemon and network configuration issues quickly and efficiently. The information available for storage and security has been helpful, despite some challenges in those areas along with conducting DR exercises.

The steps I needed to take when setting the solution up involved starting with dockerizing the application on CentOS, primarily with versions 7/8. I pulled the Docker image after setting up CentOS and created user groups to prevent overwriting. Using the daemon setup, I configured the firewall and created the Docker file. My workflow continued with using Maven version 3.8 and integrating it with Eclipse to enhance several endpoints. This included updating PL/SQL procedures and aiming for an SLA of less than one second, with a multi-stage deployment reflecting the expanding functionality of our application.

From my perspective, the experience with the deployment of Docker on CentOS is quite positive, especially for the CI/CD pipeline. The installation is straightforward with easy updates and configurations, including starting Docker groups and handling the daemon without challenges. I utilized a JSON-based setup, firewall setups were simple, and the multi-stage deployments were effective. My integration efforts with Maven and Eclipse were also seamless, leading to a flawless push to ECR.

Docker on CentOS is utilized in a hybrid setup within my organization; starting on-premises with CentOS, our architecture evolved to the cloud. I began with building everything locally, then transitioned to development environments, eventually versioning the applications and pushing to ECR, allowing flexibility whether on local or cloud resources.

In terms of reliability and stability, I find Docker on CentOS to be dependable, with good kernel support and daemon stability. I would rate this solution an 8 out of 10.

Hybrid Cloud

Amazon Web Services (AWS)

My main use case for Docker on CentOS is that it can be very useful for QA and performance testing because it gives the team a consistent and repeatable environment. One scenario where I would use it is running automated API or UI test suites inside Docker containers on a CentOS-based server. Instead of depending on each engineer or local setup, we can define the test environment with a Dockerfile and Docker Compose, including the test framework, browsers, dependencies, environment variables, and reporting tools.

I decided to use Docker on CentOS for my testing environments because, from a performance perspective, Docker helps reduce setup time and improve test execution consistency. For example, we can run tests in parallel containers, isolate services, and compare results more reliably between local, staging, and CI environments. However, it is important to monitor CPU, memory, network usage, container startup time, and disk input and output because poor configuration can create false performance issues that are not related to the application itself.

The best features Docker on CentOS offers include stability, repeatability, automation, and performance control. I think that for testing teams, Docker makes it easier to package the full QA environment, run test suites in parallel, control dependencies, and reproduce performance results. It integrates well with CI/CD pipelines and allows teams to scale test execution without manually configuring each CentOS server. My main recommendation is to use and maintain CentOS stream versions, define resource limits, avoid running containers as root when possible, and include logs, reports, and monitoring as part of the implementation.

Automation and performance control specifically have helped my team mainly by making execution more predictable, repeatable, and easier to scale. For example, in a recent project, we needed to run automated regression tests against multiple environments. Before using Docker on CentOS, every machine or server had small differences, such as different node versions, browser versions, drivers, dependencies, or missing packages. That created false failures, wasting time debugging the environment instead of the application. By moving the test execution into Docker containers and CentOS, we packaged the full test environment: framework, dependencies, browser configuration, test script, reporting tool, and environment variables. This made the automation much more stable, so every execution used the same baseline. An example of a challenge it solved was an unstable regression execution where tests were failing randomly because the host machine was under heavy load, especially when several suites were running at the same time. After containerizing the execution, separating services, and monitoring resource usage, we gained better visibility into bottlenecks, enabling us to identify when a container needed more memory, when parallel execution was too aggressive, or when the application response time was actually slow. The main benefit was that Docker on CentOS gave us a controlled testing layer. Automation became easier to maintain, performance results became more trustworthy, and at the end of the day, the team spent less time fixing environment issues and more time improving test coverage and product quality.

Docker on CentOS has positively impacted my organization because I know that many projects are using Docker on CentOS. The impact is positive because it provides us with a more stable and repeatable way to run automation, testing, and supporting services. One of the biggest benefits has been environment consistency. Before using Docker on CentOS, different servers or local machines could have various versions of Node.js, Java, browsers, drivers, or system packages, causing false test failures and making debugging slow. With Docker on CentOS, we were able to package the required dependencies into images, so our execution was the same.

I mentioned many benefits, but I have noticed some areas for improvement.

Some needed improvements include clearer installation and version compatibility. Docker's official documentation currently lists maintained CentOS Stream 9 and 10 as supported for Docker Engine. Teams using older CentOS versions need to be careful with compatibility and support planning, so clearer migration guidance for older CentOS versions would be beneficial. Another area is in troubleshooting; it could be made easier. When Docker fails due to networking permissions, CI, Linux storage driver, or daemon configuration, the error messages can be too technical. A guided diagnostic tool for CentOS would be very useful, checking repositories, kernel compatibility, firewall rules, the overlay, Docker daemon status, and container resource usage. Additionally, performance visibility could be improved as Docker already provides resource control, but for QA and performance testing, better built-in dashboards for CPU, memory, disk, input/output, network latency, container startup time, and test execution would help in understanding performance issues. Security defaults could be stronger and easier to apply because features like rootless mode are available, but clearer recommendations and simpler setup flows for running containers with least privilege, managing secrets, scanning images, and avoiding risky volume permissions are needed. Lastly, container integration and delivery in QA could be better documented, as Docker works well with automation pipelines, but more official examples for CentOS-based Jenkins, GitHub Actions, self-hosted runners, GitLab, browser testing, API testing, and performance testing documentation would help QA teams adopt it faster.

I have around ten and a half years of experience in my current field.

Docker on CentOS is stable, which is why we chose it, as it requires fewer resources than virtual machines.

Docker on CentOS is highly scalable for our use cases. It allows us to move from a single machine or manually configured test execution to a more flexible model where we can run multiple containers in parallel, isolate workloads, and scale tests based on available CPU or memory.

From our side, customer support has been great, especially when we encountered some issues.

Before choosing Docker on CentOS, we evaluated options including virtual machines and manually configured setups.

Other options we evaluated included Jenkins, manually configured CI/CD agents, and manual Kubernetes.

For our private or hybrid deployments, we use various cloud providers, including AWS, Google Cloud, and Azure. My experience with pricing, setup cost, and licensing has generally been positive. The initial setup cost was more related to infrastructure, configuration, and monitoring. Once the Docker images and pipelines were standardized, the long-term costs became easier to manage because we spent less time fixing environment issues and more time executing tests. From a licensing perspective, Docker Engine on Linux is licensed under Apache, while Docker Desktop has a separate subscription. Overall, I would say that the pricing and licensing experience is reasonable, but it requires good governance to clarify the distinction between server-side Docker Engine usage and Docker Desktop usage, track who needs paid subscriptions, and include cloud compute, storage, networking, image registry, and monitoring costs.

We did not purchase Docker on CentOS through the AWS Marketplace. In our case, Docker was deployed on our VMs and CentOS-based servers or cloud virtual machines, mainly as part of our internal infrastructure. Before using Docker on CentOS, we mainly relied on more traditional setups, such as dedicated virtual machines, manually configured Jenkins agents, and local development or QA environments with dependencies installed on the host machine. The primary reason we switched to Docker on CentOS was to reduce environment inconsistency. Different servers could have various versions, which led to issues during execution. Docker on CentOS provided us with a more repeatable and controlled execution environment.

For example, in one project, we saw several positive and measurable outcomes, especially around test execution stability and environment consistency. One major improvement was reducing the time spent preparing and fixing test environments. Before Docker on CentOS, a lot of time was lost because different machines had different versions of Node.js. After containerizing the test execution, the setup became much more predictable because the same Docker image was used across local, staging, and CI environments. In terms of outcomes, we saw improvements such as less troubleshooting time, faster onboarding, more stable automation, better parallel execution, and cleaner CI/CD execution logs. We now have logs, reports, and artifacts that are easier to collect from each container. A practical example is the regression testing, where previously, when a test failed, the team often had to check whether the problem came from the application, the server, the browser version, or the local configuration. With Docker on CentOS, we had a standardized execution layer that reduced false failures and made debugging faster. From a performance control perspective, Docker on CentOS also helped avoid overloading the host server by defining memory and CPU limits, allowing us to better understand whether a slow execution was caused by the application, the test framework, or the infrastructure. This made performance results more reliable.

My experience with pricing, setup cost, and licensing has generally been positive. The initial setup cost was more related to infrastructure, configuration, and monitoring. Once the Docker images and pipelines were standardized, the long-term costs became easier to manage because we spent less time fixing environment issues and more time executing tests. From a licensing perspective, Docker Engine on Linux is licensed under Apache, while Docker Desktop has a separate subscription. Overall, I would say that the pricing and licensing experience is reasonable, but it requires good governance to clarify the distinction between server-side Docker Engine usage and Docker Desktop usage, track who needs paid subscriptions, and include cloud compute, storage, networking, image registry, and monitoring costs.

Before choosing Docker on CentOS, we evaluated options including virtual machines and manually configured setups.

Other options we evaluated included Jenkins, manually configured CI/CD agents, and manual Kubernetes.

I have some additional suggestions regarding my main use case or how Docker on CentOS fits into my testing workflows. My main suggestion for implementation is to use official Docker repositories and maintain CentOS version. Docker currently documents CentOS Stream 9 and 10 as supported for Docker Engine, while CentOS Linux 7 reaches end of life on June 30, 2024. Therefore, I would avoid using old CentOS versions for new implementation to avoid issues.

I have one suggestion for teams implementing Docker on CentOS. It may be best to start with a simple Docker image for the test framework, then add Docker Compose if multiple services are needed. After that, I recommend defining the CPU and memory limits, collecting logs and reports from each container, and integrating the execution into the CI/CD pipeline because that workflow creates a clean and scalable foundation for both automation and performance.

My advice for others looking into using Docker on CentOS is to start simply but implement it with good governance from day one. Docker can bring significant value, but only if the team standardizes how images contain logs, resources, and security are managed. The most important recommendation is to use a supported CentOS version, standardize your images, integrate with CI/CD early, control CPU and memory usage, monitor container metrics, and think about security from the beginning.

Regarding Docker on CentOS's AI capabilities, I think governance and security are critical. Docker on CentOS can serve as a strong foundation for AI workloads because it provides isolated, repeatable, and scalable environments. However, AI use cases usually involve sensitive data, dependency models, credentials, and automated decision-making, so organizations need strong controls around image creation, access permissions, secrets, and vulnerability scanning. From a governance perspective, I recommend clear standards for approved base images, image versioning, access control, and audit logs. From a security perspective, I suggest running containers with less privilege, avoiding root execution when possible, scanning images, generating S-BOMs, and keeping the CentOS host updated. Docker supports rootless mode to reduce risks from the Docker daemon and container runtime, while Docker Scout can analyze images using S-BOMs and vulnerability data. It is also essential to be cautious with CentOS version support, as Docker Engine documentation currently lists maintained CentOS Stream 9 and 10 as supported. Using outdated CentOS versions creates governance and security risks. Overall, I view Docker on CentOS as a positive foundation for AI and automation workloads, provided it is implemented with strong governance, controlled images, secure measures, vulnerability scanning, resource limits, and clear ownership of the container.

Regarding Docker on CentOS's AI capabilities, I see accuracy and reliability as different aspects. Docker on CentOS itself does not make an AI model more accurate; accuracy depends on the model, training data, prompts, configuration, and validation process. However, Docker on CentOS can strongly improve the reliability and repeatability of the output by providing a controlled environment where the same model, dependencies, libraries, and resource limits are used each time. In an AI testing or automation scenario, Docker on CentOS can help ensure that the same model version, Python libraries, CUDA, or CPU configuration, and environment variables are used across local, staging, and CI environments, reducing inconsistent behavior caused by dependency differences. Additionally, the Docker model runner also supports managing and running AI models locally, configuring model parameters, and displaying prompt response details, which can help with traceability and repeatable validation. From a QA perspective, I would not trust AI output solely because it runs in Docker on CentOS. I would still recommend automation, automated validation, expected output checks, prompt versioning, model versioning, logs, and human review for critical cases, along with monitoring for hallucination or unstable responses. Overall, I would say that Docker on CentOS is reliable as an execution platform for AI workloads, especially when properly configured, but the accuracy of the AI output must be measured separately through testing benchmarks and business validation. Since Docker Engine officially supports maintained CentOS Stream 9 and 10, I would also avoid outdated CentOS versions for AI workloads that require strong reliability and security.

Hybrid Cloud

Other

My main use case for Docker on CentOS is to deploy our web app only. Docker is the centralized space where we can collate all our codes to run in a centralized environment. We have an embedded app which is hosted on the website, where we can use Docker to deploy our app. It acts as a mini virtual environment for our apps to run and compile on the server.

A specific example of a web app I have deployed using Docker on CentOS is a web app for a car-related company. They wanted to analyze their sales for a particular quarter, so we created a React-based web app where we used the Docker environment for compiling our Django app, which serves as the middleware server.

We have deployed a couple of apps using Docker on CentOS. We mainly use Docker for our Python-based web apps to be deployed, which act as the middleware server. We have also used a MongoDB-based app in Docker, and it is quite helpful.

In my opinion, one of the best features Docker on CentOS offers is the ability to define all the library versions and Python versions that are compatible with my project. I do not know of any other CentOS solutions that enable us to use these features on their servers or websites. However, in Docker, I can use a dedicated Python version and dedicated libraries that I need for my app, which is very helpful for ensuring my app works seamlessly on the website.

Having control over library and Python versions helps my workflow because we started this development a couple of months ago. At that time, we used the latest Python version 3.9, but now Python 3.14 has come out. The libraries compatible with Python 3.9 are specific to that version, and there have been syntactical changes in Python 3.14. I want to deploy my app specifically in the 3.9 Python version, which is why I use Docker to deploy my app. It is very helpful because it compiles all my libraries using the Python 3.9 version only.

In terms of scalability, Docker on CentOS is very helpful because we are currently using the Linux OS. However, if we want to use Windows or any other operating system that is specific to our particular app, we can do that in Docker. That is an added advantage. We can also create multiple Dockers to communicate with each other. Even though Kubernetes is a separate topic, Docker's capabilities are quite helpful.

One improvement I would like to see in Docker on CentOS is how sometimes when I try to install the recommend.sh file, it fails with timeout errors on the server side. It would be better if those kinds of issues are improved within Docker. Although Docker has excellent community forums, where we can analyze and search for any doubts, resolving the timeout error would enhance my experience and make it easier to use across any web apps. That is my suggestion.

Docker on CentOS is already quite good, and it has very good community forums and a helpful website. Other than that, I find Docker on CentOS to be exceptional.

I have been using Docker on CentOS for the past two years.

Docker on CentOS is very stable in my experience.

Docker on CentOS's scalability is impressive, as it handles growth and expansion very well for our apps. It is compatible with all operating systems including Linux and Windows, making it easy to scale, and we can use it for multiple regions as well.

The customer support for Docker on CentOS is excellent, as there are very good community forums. Whenever we run into issues, we can turn to these forums, where we can easily find solutions by pasting the errors we receive. Many tech experts have contributed to the forum, making it easy for us to get help.

We have not used any different solutions before Docker on CentOS; we have been using Docker from the start.

I have seen a return on investment with Docker on CentOS, especially in terms of time saved. Compared to other deployment processes, Docker significantly reduces our deployment time. Previously, it took us about a week to deploy, but now we can deploy our entire app in one or two days.

Regarding pricing, setup cost, and licensing for Docker on CentOS, everything is handled at the on-premises level. My company manages everything, so we do not need to pay any extra fees for that; we pay a total organizational amount and utilize it.

Before choosing Docker on CentOS, we did not evaluate any other options; Docker was our first preference.

Docker on CentOS has positively impacted my organization because, deployment speed-wise, it is similar to other CentOS apps, but Docker is user-friendly. Even a non-coding person can leverage AI's help to write Docker code easily. It helps create working directories and manage any libraries or folders I need, so I can operate in a straightforward, human-friendly manner, making Docker very helpful.

This user-friendliness has impacted my team significantly because we are in an organization that is not tech-dependent. If we need to host a tech-dependent app, we typically have to learn everything from scratch. However, using Docker bypasses the need for extensive technical knowledge. I can create a Docker app without any tech knowledge by utilizing human-readable formats and the help of AI and Google, allowing me to compile my web app on a Django server using Docker. It is extremely beneficial.

I rate Docker on CentOS overall as an eight out of ten. The reason I choose eight out of ten is because, while I would like to give a perfect score, there are some timeout issues and other challenges with Docker. If those could be resolved, that would improve my satisfaction. Besides that, there are great community resources and forums available for Docker that are very helpful, and I do not feel any other changes are needed from Docker's side.

I definitely advise others to go for Docker on CentOS instead of any other options. As I mentioned, it is very user-friendly, requiring no technical knowledge, and anyone can write Docker code in my opinion, so I encourage people to proceed with it.

On-premises

Docker on CentOS is primarily used for application containerization in our organization. We create Docker images and conduct comprehensive testing through our users and application testers. In addition to testing, we use CentOS machines for DevOps tools, and we find that images of databases, Kubernetes, MySQL, Redis, and Apache are very convenient to use without needing to install them directly on Docker.

Recently, we were assigned a task to set up a Python Flask app, so we created a Docker image on our CentOS machine, which we have been using for the past year. Since the CentOS machine still had available resources, we utilized it and created a Dockerfile for a Python Flask app. We also created another image to use the MySQL database, and when we ran Docker compose up, it started working properly. We then handed over this machine and image to the application team for their further testing.

The most valuable feature of Docker on CentOS is that both CentOS and Docker are free and open source, so we do not need to pay any extra cost to run our testing on these resources. All Docker images are also free, and whenever we require any other image, we simply run the command docker run with the image name.

We do not need to install those packages on our system or download those other libraries on CentOS. We simply run those images and that is it. This approach is very helpful for us rather than downloading numerous pieces of software on our systems. Since Docker is mainly used for containerization of applications, it is very impactful for our application team. They do not need to use their legacy systems of installing language packages and then downloading those libraries.

Previously, it could happen that on one server, one application would work fine due to those libraries, while another application would not work because those libraries and functionalities were not available on those systems. This was a time-consuming process that both the application team and the operations team had to endure. Since the introduction of Docker, we simply run those Dockerfiles and download those images from the Docker repository itself, and we can run our production or testing smoothly.

Running on CentOS is an additional advantage because CentOS is completely free. Versions seven, eight, and nine are very robust and do not show many bugs. These are very stable systems, and stable systems provide great positivity to our organization. When we are working on a Python Flask application, we simply run the image, and we run the command docker run and it will fetch the image from the Docker repository, making it easy for us to use.

On another occasion, if we receive an application for Node.js and need to perform testing on it before it goes into production, we need to perform heavy testing from our team, our application team, the testing team, and then the UAT. We do not need to install those packages or software manually; instead, we download directly from the Docker images.

This approach is saving us cost and also saving us a significant amount of time. We do not need to maintain any repository server that holds all this software, and we do not need to copy or update those software packages day-to-day. This is saving us a lot of cost, a lot of time, and a lot of manual work.

I think more stability could be improved, and there could be much more community support. There is good community support for CentOS mainly, but I think there could be a dedicated community for Docker for those people who are using Docker on CentOS. It could be very helpful. Sometimes, legacy systems do not work because those images are not available. If there were community support specifically for Docker on CentOS, we could ask other people if they have those images or libraries available, which would help us or others trying to run or test their legacy systems on CentOS.

I rate this nine out of ten because I still think it is not perfect. Even though it is free and open source, it still needs some more robust features to compete with systems such as Red Hat or Ubuntu. Since we are not using Docker on CentOS for our production work, only for testing, if it could be more robust and scale its features, it could compete with Red Hat and Ubuntu, and then all of us could use Docker on CentOS for production too.

I have been using Docker on CentOS for over two years.

It is stable. We have been using Docker version seven through nine until today. We found a few issues sometimes, but they could relate to our application too. We are not entirely sure whether the issues are with Docker on CentOS or the application, but we would say that if the application is working today on Docker on CentOS version seven, it will continuously work on Docker on CentOS version seven unless we make any changes or migrate our application from Docker on CentOS version seven to Docker on CentOS version nine.

The scalability is good. We can simply add those resources to the system, and we have tried to scale our applications from ten users to one hundred. It works well, and we have not faced any issues with scalability.

Since it is open source, there is no dedicated customer support available for Docker on CentOS, but there is a community which is very handy and useful. We have asked many questions in the community and have received very good support from those people.

In my company, Docker was the first choice for containerization. We did not use any other containerization tools, and it works very well with Docker on CentOS, so we did not consider any changes.

The main advantage of Docker on CentOS is the money saved. We are not using any Red Hat or any Ubuntu or any Alpine Linux machine, which would cost us licensing or support. Docker on CentOS is completely free. That is the main factor I would mention. It has saved us the cost for the operating system. Fewer employees are needed because we are not maintaining any other repository server which contains all those images and software.

We used to download those software packages every month so that our application could test those packages. This is how we have saved cost on the repository servers and very few employees are needed just to maintain or test on these Docker on CentOS machines.

For the server side, we do not need to pay any cost. Earlier we were using Red Hat and Ubuntu, so we do not need to pay any cost for the image, for the licensing, or for the support. The cost has become very minimal, less than five percent since we started using Docker on CentOS. In terms of time, we are not downloading those software packages every month so that our application should run on the latest systems. This is how we have saved a repository server. We are not maintaining any repository server which contains all those images and software. The cost reduction is less than five percent, and for manual work, the number of resources has reduced from ten to three or four only since we have started using Docker on CentOS.

There is no cost associated with either Docker or Docker on CentOS. It is completely zero cost. There is no licensing needed for it, so we can use it as freeware on our on-premises systems. The only cost associated is our VMware. There is nothing cost-related with Docker or Docker on CentOS.

I would advise others looking into using Docker on CentOS that if they want to reduce costs and test their application without paying any additional amount, or if they think they can use a smaller version of their Linux system, then Docker on CentOS is the best choice. I rate this product nine out of ten.

My main use case for Docker on CentOS is that we have a whole Kubernetes cluster running, and Docker is a part of Kubernetes, so we just use it. When I want to run a container, I use Docker on CentOS system.

A quick specific example of how I use Docker on CentOS in my work is that initially we had Docker Compose. When we didn't have a Kubernetes system, we were using a Docker Compose YAML file through which we deployed all the Docker containers on our CentOS system. We created a Dockerfile for our application, and then we used databases such as Redis, MySQL, and other tools which were running as a Docker container, and we deployed it in our system.

Regarding my main use case or any other ways I use Docker on CentOS, the main use case is the deployment itself. We use Docker to deploy our application as well as other dependent resources.

The best features Docker on CentOS offers, and what I loved the most, is that we can build a single Dockerfile and build an image for it and then share it with anyone in our team or anywhere, to the customer or anyone who wants to run that application. They just need to have Docker installed on their system and they can easily run it.

Using Docker on CentOS helps my team and makes our workflow smoother because we don't need to worry about the way we ship, the way we share the images, or share the product itself. We have Docker; we can write a simple Dockerfile for the application, and then we can easily share it with anyone we want to, so I think that's the best part.

Docker on CentOS has positively impacted my organization as it made our workflow quite easier. Initially, when we didn't have the Kubernetes system and used to run our product directly on a system, when Docker came along, it really simplified everything.

Docker on CentOS made my workflow easier since the deployment was quite fast after switching to it. We don't have to build everything every time we want to run; we have a Dockerfile, we just build a binary of our application. We use Golang, so we build a single binary and then just build the Docker on CentOS image for the application and we are good to go.

Regarding how Docker on CentOS can be improved, I wouldn't say there are any major issues. The compatibility is quite good. Docker can be easily run on the CentOS system. We just need a yum command to install Docker, and after that, it's quite the same as every other application that we have, so overall it's good.

I think there are sometimes issues with CentOS systems as such regarding Docker; it misbehaves sometimes. Most of the time, I would say 99.9% of the time it works. There are some scenarios where sometimes we might face some issues on CentOS systems.

In terms of accuracy and reliability of output from Docker on CentOS's AI capabilities, I wouldn't say it is 100% accurate. Sometimes it does hallucinate, but overall it's good.

I have been using Docker on CentOS for four years since the start of my career.

Docker on CentOS's stability is quite good. Overall, it's quite usable and there's nothing to worry about.

Regarding Docker on CentOS's scalability, it's quite easy to deploy and scale it as well.

Customer support for Docker on CentOS is good. Whenever we are stuck, we get customer support easily. On a scale of 1 to 10, I think overall customer support for Docker on CentOS is good.

I did not previously use a different solution before Docker on CentOS. I think we started with Docker itself; earlier we were using just a bare minimum application to deploy it, but eventually, when we got to know Docker, we felt it's quite good to use, so we started using it.

My experience with pricing, setup cost, and licensing for Docker on CentOS is that it's quite easy to set up, so I think it was not that tedious.

I have seen a return on investment with Docker on CentOS; time is the major factor here. In our case, it was quite easy to use it and deploy it, so that is one of the main things that we observed.

My experience with pricing, setup cost, and licensing for Docker on CentOS is that it's quite easy to set up, so I think it was not that tedious.

Before choosing Docker on CentOS, I did not evaluate other options. In our case, we just went with Docker because we felt it's quite easy and it's something that we need to use.

It's quite easy to learn Docker on CentOS. I think the learning curve is not steep; it's quite easy. You don't have to worry much. You just need a Docker command, and then you just need to know the simple commands and you can easily run it.

I would rate Docker on CentOS as a 10 out of 10 because it has really made our workflow quite easy to deploy on a system. I chose 10 out of 10 for Docker on CentOS because I think the ease of deployment and ease of using it is unmatched. We don't have any significant learning curve; we just need to know how exactly a Dockerfile works and a couple of commands for Docker and you're good to go. You can easily build your images and then deploy it anywhere you want to.

Regarding Docker on CentOS's AI capabilities, I would say it's good. I see that due to the AI feature, if we are getting stuck or need some commands or anything, we are able to just get it through the AI, so that is good. Docker on CentOS is deployed in our organization on a public cloud.

My advice to others looking into using Docker on CentOS is to use it because it will really make your workflow easier and quite fast. In terms of business relationship with this vendor, we are just a customer; we don't have any other relationship. My overall review rating for Docker on CentOS is 10 out of 10.

Public Cloud

Google Cloud

My main use case for Docker on CentOS is to deploy Docker containers and build Docker containers.

A quick specific example of how I use Docker on CentOS in my day-to-day work is to deploy a container with a specific business application and microservices, create a microservices environment, and create development and production environments.

Anything which can be delivered with Docker is included in my main use case for Docker on CentOS.

The best features Docker on CentOS offers are everything which Docker is able to do, including multi-stage builds, secure Docker containers, the ability to deliver Docker containers, and run them in different workloads.

Multi-stage builds and security features help me in my workflows by creating empty, optimized containers or optimized images for future deployment without unneeded tools. For example, build tools or build packages are removed, so the final image is much smaller and does not include anything that may have vulnerabilities. Additionally, it does not have any layers which could be used by hackers for system attacks.

Docker on CentOS has positively impacted my organization by allowing us to deliver identical solutions to development and production environments, making it easier to deploy new versions, debug versions that we have in other environments, and utilize many pre-built images available in Docker Hub and the official Docker registry.

Docker on CentOS could be improved by delivering the latest versions faster because CentOS does not always deliver the latest versions of Docker. However, in general, it works great.

I have been working in my current field for twenty years.

Docker on CentOS is absolutely stable.

I encounter no issues with scalability, and it is working great.

Before Docker on CentOS, I mostly used virtual servers without any containerization, but I switched because Docker has great features and containers allow you to do much more and faster.

I have seen a return on investment because when you do not need to set up the infrastructure or you use vendor containers, you can utilize ready-to-use solutions in minutes versus spending a few hours building it by yourself.

My experience with pricing, setup cost, and licensing is based on using the open-source community version, which means there was no pricing or licensing, only the cost of the resources used.

Before choosing Docker on CentOS, I evaluated Docker on Ubuntu.

My advice to others looking into using Docker on CentOS is that it is stable and reliable. I rate Docker on CentOS an eight because a faster release of the version of Docker would make it a ten for me.

Hybrid Cloud

Amazon Web Services (AWS)

We have servers running operating systems like Ubuntu and CentOS. Regarding Ubuntu, we are interested in LAMP stack, Ubuntu, or Jenkins on hardened Ubuntu, but we are not using LAMP stack. We are using Ubuntu and then MySQL in a different way, but not LAMP stack. For CentOS, Docker is there, but we are using PostgreSQL, not MariaDB. Docker on CentOS is what we are using. It has been about six years since we started using Docker on CentOS. It is running one of our systems hosted there, on our document management system.

How fast the application runs is one of the biggest advantages for me in Docker, but on the downside, issues to do with space utilization arise sometimes. Since we implemented it, the system really improved and became responsive very fast. When you have limited space, the system tends to crash from time to time, so you have to ensure that you have enough space at any one point.

We are using the orchestration feature in Docker. That was the main motive for having orchestration; it helps better manage the containers.

I am comparing Docker on CentOS with the one that is running on Ubuntu, and in terms of scaling up, it is easy to work with when it comes to that. That is the main feature I have been benefiting from.

Because it was first, we recently did it on Ubuntu, but initially, it was running on CentOS. We were comparing and seeing which one runs better, but I realized on Ubuntu it is much easier to work with.

The lightweight architecture on CentOS affects my resource utilization significantly.

Crashes are the main issue I see. I have not really noted down specific metrics, but I realize that when it comes to disk space utilization, it really goes up so fast. We are not using a CI/CD pipeline in Docker. The main issue comes from running out of space; that is when crashes happen, and that is the only thing I have seen as an area for improvement in Docker.

I have been working as a customer with Docker mainly for around six years.

Mainly, the support we get is from online communities in case of any challenges, and there may be some people around who have more expertise in that area; that is how we have been managing. We have not gotten into a state where support is complex, but most things can be easily found as resources online to help resolve those issues.

It is quite complicated to install Docker on CentOS; it is not as easy as it is on Ubuntu.

Mainly, it is about time with Docker; I think it helps us save in that way, and using open source has been helping us not to invest in that. I could say it is maybe forty percent compared to before using Docker.

The lightweight architecture on CentOS affects my resource utilization significantly. I have not really noted down specific metrics, but I realize that when it comes to disk space utilization, it really goes up so fast. We do on-premises deployment mainly with Docker on CentOS, so we have not explored the cloud aspect. Because it was first, we recently did it on Ubuntu, but initially, it was running on CentOS. We were comparing and seeing which one runs better, but I realized on Ubuntu it is much easier to work with. Mainly, the support we get is from online communities in case of any challenges, and there may be some people around who have more expertise in that area; that is how we have been managing. I gave this review an overall rating of seven out of ten.

On-premises

Other

My main use case for Docker on CentOS is for running websites and backend services. I use Docker on CentOS for running websites, specifically for APIs and for running NGINX service.

I used Docker on CentOS for a microfinance application that had more than 16 services at that time for the backend. The logic was basically on Node.js, and I used all those microservices on Docker on CentOS. Later on, I used the same service on ECS Fargate.

The best features Docker on CentOS offers include its lightweight containers and fast startup. Whenever there was a scale-out required for the APIs, it was immediate, less than 10 seconds to boot up, which was very helpful for the microfinance services.

The fast startup and lightweight containers of Docker on CentOS were very helpful because earlier when we used to have these APIs running on the EC2 instances, many instances were required for those services, even though the code was very small. We had to use many EC2 instances instead of using microservices or micro containers like Docker. When we moved to Docker, the scale-out was very fast and very helpful for the business. The boot time with Docker was very less compared to the EC2 instances because running on the EC2 instances required more boot time for the OS, and there was a long delay due to the script execution for a few seconds.

Docker on CentOS has positively impacted my organization as it helped us grow the business, and the customer was very happy with the services, thus revolutionizing the business.

Docker on CentOS can be improved by being in sync with the OS updates. The OS is already very compatible with Docker, but it can enhance functionality similar to Kubernetes regarding container orchestration, allowing it to compete with other tools.

The metrics of the containers in Docker on CentOS can also be improved, along with the monitoring part which needs enhancement.

I have been using Docker on CentOS for the last four years.

I would advise others looking into using Docker on CentOS that rather than using their services directly on the EC2 instances which costs higher and take more time to boot up, they should go with Docker containers, which are very fast, easy to deploy, and manage, allowing many services to run on the same EC2 instance without dependencies. If a service needs Node.js version 7 and another needs Node.js version 10, there might be conflicts when running directly on EC2 instances, but with Docker containers, these issues do not arise. Moving to microservices like Docker is the best choice rather than directly installing on the EC2 instances. I have covered all the important areas regarding Docker on CentOS. My overall rating for Docker on CentOS is 9 out of 10.

Amazon Web Services (AWS)

My main use case for Docker on CentOS is to provide infrastructure-related support for one of my clients who has their own environment, along with performance testing tools, so we set up Docker on their CentOS servers.

A specific example of how I use Docker on CentOS for performance testing or insulated support is when the client needs to test their application on their environment, so we install the CentOS server with our product image, spin up the container, and test a few use cases.

Regarding my main use case for Docker on CentOS, I face challenges with Docker sometimes having network-related issues, which require us to restart the Docker daemon, but apart from this, I am not facing any other issues with Docker.

The best features Docker on CentOS offers are that it works equally well on CentOS as it does on Ubuntu or RHEL, though for one or two specific use cases, we set up Docker on the CentOS environment for our client only.

The compatibility of Docker on CentOS is really smooth, and I have not faced any kind of issue.

Docker on CentOS has positively impacted my organization because I manage the client's environment, and since CentOS is a free version for RHEL servers, they use it for cost criteria, and Docker works smoothly on CentOS.

I cannot provide specific outcomes or metrics related to efficiency, cost savings, or performance improvements since using Docker on CentOS in the client environments due to limited access, but I believe they use CentOS for Docker setup for cost-saving, and Docker is stable as an OS for RHEL freeware.

I am not facing any performance or compatibility issues on Docker on CentOS that need improvement.

Docker sometimes has some network-related issues, such as the host network not working, so we switch to a different type of network, and regarding CentOS, we are not using any support since it is freeware, relying only on documentation which serves as our support.

I am not finding anything that Docker on CentOS needs to improve because its documentation covers everything that works as expected.

I have been using Docker on CentOS for around four years.

Docker on CentOS is stable.

The scalability of Docker on CentOS depends on the hardware; if you have good hardware, you can scale Docker on CentOS as required.

I have not used the support for Docker and CentOS since both are free resources, and I do not believe we need support for this.

Before choosing Docker on CentOS, I evaluated other options such as Ubuntu, as I have used it for our environment, but Docker on CentOS was chosen for the client requirement.

My experience with pricing, setup cost, and licensing for Docker on CentOS is very favorable as CentOS is free of cost and does not require a purchase license, and the same applies to Docker without needing any specific license, but we do need manpower knowledgeable in Docker on CentOS for installation.

We use AWS as our cloud provider for Docker on CentOS.

I have seen some money saved because when someone requires a RHEL-based OS with Docker, CentOS is the best choice due to being freeware, making it easy to set up on that machine.

My experience with pricing, setup cost, and licensing for Docker on CentOS is very favorable as CentOS is free of cost and does not require a purchase license, and the same applies to Docker without needing any specific license, but we do need manpower knowledgeable in Docker on CentOS for installation.

I am not using any different solution.

My advice for others looking into using Docker on CentOS is that if your client or company requires an RHEL-based environment and needs Docker, you can set up Docker on CentOS servers easily for testing, and if a subscription-related task is needed, then consider switching to an RHEL subscription.

I do not have any additional thoughts about Docker on CentOS. My overall review rating for Docker on CentOS is ten out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use case for Docker on CentOS is for local development, tests, and creating new server and server test applications, making the integration from staging and the production environments. Some of that work was applied at Johnson & Johnson.

A specific example of how I use Docker on CentOS in one of those situations is that we create staging development sites using CentOS as the original VM application and inside of these VMs, we put Docker and configure the containers inside of it to make the IP configuration easier on CentOS. We can also create a good network interface and network jobs between the different VMs. We used to isolate some databases in Docker containers in different stages, using CentOS to separate these stages. We can also create some network environments and share folders between the different VMs using CentOS.

Last week, I built a Proxmox server with some VMs using CentOS and integrating not only Docker but also cPanel configured by me inside of my Proxmox. I created the environment to make the replication of the tenants from different clients automatically using Node.js as a backend and creating automatically with Terraform and using CentOS as the main image to use in our environment.

The network integration of Docker on CentOS makes my workflow easier because when I create a new tenant in my environment, I just build a VM with this configurator inside of my ecosystem. I integrate the creation of new VMs and the tenants using Terraform, integrating with CentOS, and inside of this CentOS image, I put Docker and containers, which I use to isolate some clients. However, I need to have access from my tenant manager to create the folders and share them. The containers are isolated between the VMs, but the VMs have some access between them to get some configuration from the original Proxmox environment configurator.

I have some Grafana and Prometheus applied to these servers, and I made some measures about the improvement in file transfer between them, which shows an improvement of 20% from the last Ubuntu applications. The easier monitoring between the VMs using that shared folder is also a very useful tool.

Docker on CentOS impacts my organization positively because it is a very useful tool to create a strategic environment where we can plan every container with what we need to do between them. CentOS is a great solution to create the background environment and connect my tenants using my tenant evaluator. With this, I can easily create the environment, network isolation, and sharing folders that we need to share between them.

The best features Docker on CentOS offers are the configuration of the network between the VMs and the integration of this network with Docker, which is the easiest thing that we can use with these environments. When we talk about Ubuntu or other options, sharing this network and sharing the folders between them is a little bit difficult in comparison with CentOS.

Docker on CentOS can be improved by using the Terraform creation, pointing for a smaller CentOS version that we can create to just take exactly what we need to consume in our image. Instead of getting a full version of CentOS, we can take the small version and only install what we need on the server. This can be very useful to make more space for our clients.

I think Docker on CentOS could benefit from images that we can create or have, for example, just a module based on Portainer or some UI interface to create the containers automatically or create some internal APIs to make it easier to configure this by Terraform.

I have been using Docker on CentOS since 2016.

Docker on CentOS is very stable.

My setup of Docker on CentOS allows for horizontal scalability; I can upgrade memory and processors, and CentOS automatically scales when we make adjustments inside of the VMs. Docker will adapt to these adjustments using the correctness in the Dockerfile.

My customer support is automated by AI; therefore, I don't have specific feedback about support teams related to CentOS.

I have never needed help from support teams; I find the documentation very well formulated and easier to implement.

Before using Docker on CentOS, I used Ubuntu, but the size of the image for Ubuntu was not optimal, making it harder to configure in Terraform. That's why I switched to CentOS.

The setup costs of CentOS include some versions without a cost, but I don't get the enterprise licensing for now, and I'm using the normal open-source licensing for CentOS.

I deploy Docker on CentOS using a private cloud and my own registry.

I have seen a return on investment; I built my own AI agents connected to my Proxmox server, which led to significant improvements in time and money saved, amounting to over 60%.

The setup costs of CentOS include some versions without a cost, but I don't get the enterprise licensing for now, and I'm using the normal open-source licensing for CentOS.

I evaluated other options before choosing Docker on CentOS, including Debian, Ubuntu itself, and FreeDOS. However, CentOS was easier to integrate and more useful when using WHM and cPanel.

Regarding the accuracy and reliability of Docker on CentOS's AI capabilities, I need to train my AI here to configure CentOS and Docker. After training, the application runs well. AI identifies applications and the configuration accurately, and we can create tools that make AI available to consume the CentOS configuration, even though I haven't yet used CentOS integrated with GPUs or AI engines.

My advice for others looking into using Docker on CentOS is to evaluate your infrastructure and do thorough planning before implementation.

The governance and security of Docker on CentOS are very good because we have a lot of tools to maintain and ensure the sustainability of that environment. This is especially true when integrating keys, and we have keys in all Linux systems, but they put the keys in one space that's easier to get. The first access of CentOS not using root is a very secure feature, as we need to make our root environment and create a root user different from the original root, which is a significant security improvement.

I have given Docker on CentOS a rating of 8.

Private Cloud

Other