Docker on Oracle Linux 10 Hardened

I use Docker on CentOS or on other Linux systems in my work, particularly for trying out new tools and for testing. It often makes sense there, and then of course also in production environments where certain settings and services should always have exactly the same state.

Docker on CentOS was made for that purpose, so that we don't keep running into the dependency problem that everyone knows: it works on my system, but not on the other one. Docker on CentOS is basically there exactly for that.

I do not have anything else to add about my use cases. Docker on CentOS itself is an excellent tool, without question. There are alternatives you can also try out, but I think as of today Docker on CentOS is probably still the most widely used container environment.

Docker on CentOS has had a positive impact on my company and my way of working because I can virtualize quickly, without carrying around all the overhead of having to check what's currently allowed, what isn't, which user can do what, or starting entire virtual machines.

Instead, I can very quickly spin up a container, see what happens, test it, shut it down, change it, and spin it up again. That's really it—the development speed is naturally fast.

When I compare it to earlier times, when everyone was working in their own virtual environment and then seeing what happens, Docker on CentOS moves more in the direction of software development. Docker on CentOS also offers an advantage here, especially when it's cross-system—when we leave the Linux world and move to other systems, it's very helpful.

I cannot really provide concrete improvements in speed or efficiency using figures or examples because it depends on what the other prerequisites are, specifically which system Docker on CentOS is running on. When I pull an image, meaning when I download it from the internet, is it already cached? If it isn't cached, what bandwidth do I have?

In a cloud environment, for example, the bandwidth is usually always good, but the underlying hardware might be good or might not be good.

Locally, I work with a powerful system and I also have good bandwidth here, so in that case a single container is sometimes faster. Additionally, when I'm developing, I'm developing on a pure Linux system, which is a bit different than if I were doing it on a Windows or Mac system, where a Linux kernel or Linux virtualization runs in the background anyway just to run this Docker on CentOS container at all.

In my view, the best features that Docker on CentOS offers are not focused on any specific function, but rather on the fact that I can put individual small work instructions in there without accessing the main system directly.

Even if it's not fully virtualized, a part of it is virtualized that I can simply run in this environment and precisely determine what is actually allowed there.

Often, even if it's only for a single task, I can use this container. That's really the big strength—it's very flexible, and I can use it for the smallest activities up to somewhat larger tasks and can also combine containers, but now we're getting into Docker Compose, which is another topic.

The function or feature of Docker on CentOS that I use the most in my daily work does not involve a specific one; it really always depends on what exactly is required at the moment. In the data engineering field, it's often the case that I need a certain base to be available, I might need a few specific drivers installed, or I might just need to run Docker on CentOS normally in a CI/CD pipeline, where it is always run.

There isn't this one special feature; instead, it's always these small parts that I outsource precisely there.

I do not have any spontaneous additions about the features or strengths of Docker on CentOS right now. For me, the big advantage is simply these small things and that I can do them quickly, above all.

Spinning up a Docker on CentOS container compared to a virtual machine is just significantly faster. I can set something up with a single command in the CLI and it's just there immediately.

In my opinion, Docker on CentOS could be improved in several ways, but that's a good question—am I missing anything?

Not really. When I think about it, it fulfills its purpose and does what it's supposed to do.

I could still add a few thoughts about possible improvements, perhaps with regard to specific use cases or wishes for the future.

Docker on CentOS in the network is perhaps one such thing, although Kubernetes actually solves that problem too—whether it solves it well is another question, but it does solve it. Whether Docker Swarm was really the best choice for smaller things, I don't know. I also don't need to have all my Docker on CentOS containers running in the network and with each other in the network that often. These are usually more individual applications.

I'd really have to think hard about what else I'd wish for there, but I don't really know.

I use Docker on CentOS not continuously but every now and then, and not necessarily always on CentOS. I mainly use Docker on CentOS itself, running on various Linux systems.

Docker on CentOS is stable in my use. Docker on CentOS itself causes few problems; it's basically mature in my opinion. Sure, something can go wrong sometimes, but overall it's very reliable.

I rate the scalability of Docker on CentOS as very good, especially when I scale it out laterally. Scaling up vertically on a machine is relatively easy; I can ultimately run as many containers as my hardware allows. I can also scale it horizontally; in smaller environments, Swarm already works quite well, and in larger environments Kubernetes is then used.

I cannot judge the customer support of Docker on CentOS; I've never used it.

Before Docker on CentOS, I did not use another solution. Actually, when Docker really came out, I started using Docker on CentOS right away. Whether Docker on CentOS was the very first, I think so, but I'm not sure. Before that there was, of course, general virtualization or software like Vagrant that I could use to try things out—that all worked too.

Docker on CentOS makes things easier later on, especially in production.

I'd rather say they were the first, and today you see that there are alternatives, in my opinion mainly due to licensing. Docker on CentOS is a tool that's very helpful, is used a lot, and the people who really use it are basically all techies.

That means you can expect these people to be able to work with tools in the open-source space and not necessarily need a vendor who requires some kind of financial compensation.

I have seen a return on investment, though I cannot provide relevant metrics or examples such as reduced staffing needs, cost savings, or time savings in a broader context. It's not just related to Docker on CentOS alone, but rather more to Kubernetes as well and how I use certain tools.

Docker on CentOS itself plays a smaller role here. It's more about the fact that I can use open-source tools compared to paid solutions, which indeed take a lot of work off your hands on one side, but also cost money.

If you know what you're doing and are willing to employ and pay the right staff, you can potentially save a good amount of money. It always depends a bit on the case and when you use these tools.

Open source is, of course, very cost-efficient, but you shouldn't forget that it isn't free; you still need people who can operate and use it.

My experience with pricing, setup costs, and licensing for Docker on CentOS has been that since I normally use Docker on CentOS on Linux via the CLI and not Docker Desktop, this question about price doesn't really arise to a major extent. For companies that use it, where I'd also have to take a closer look, Docker Desktop plays a role. That really isn't the main point here. Especially when costs do arise, people quickly switch to alternatives like Podman to avoid exactly that. Setup costs are always there of course; someone has to set it up, and someone has to maintain it.

It's naturally convenient if you can use certain service functions, but in the big picture it ultimately still comes down to a human—and in the future perhaps to AI—to set this up.

For that I obviously have to pay. Whether I pay the AI provider or ultimately the employee, the consultant, or whoever, to set up, run, and of course maintain my system.

I did not evaluate other options before deciding on Docker on CentOS. Docker on CentOS itself is used everywhere and always, and I'd say CentOS is great. However, CentOS now has the disadvantage that it's no longer supported to the same extent; instead, people are switching more to AlmaLinux, or in other areas Ubuntu or Debian are used, or nowadays simply the individual Linux systems of the cloud providers. I wouldn't cling too much to CentOS.

I rate Docker on CentOS overall a 9 on a scale of 1 to 10.

I am giving it a 9 because, as I said, it solves almost everything. Docker on CentOS is an excellent tool, and I really enjoy using it. It will probably never be perfect, so no 10.

In my view, the governance and security of Docker on CentOS in connection with AI applications are significant. Honestly, I've never used AI with CentOS and Docker on CentOS. Docker on CentOS itself and, of course, AI that spins up Docker on CentOS containers on my Linux system again and again—it works excellently.

As for how secure it is, you always have to make sure you secure the system as much as possible. That means checking what I allow my system to do and not just letting it run wild, because AI, even today, might sometimes grab things it shouldn't grab.

I cannot rate the accuracy and reliability of the results of Docker on CentOS in the AI area or in general for my use cases by pointing to specific examples, as I don't know Docker on CentOS used in the AI area; I've never really had that combination.

In general, I can say Docker on CentOS and AI work excellently together because exactly the same thing happens again: AI runs iteratively. It also has to test and try things out, and there as much as anywhere else, it makes sense to work virtualized and not directly on the system. For virtualization, Docker on CentOS is again the obvious choice because it's small and fast. The combination makes sense in my opinion and is ultimately also used.

Docker on CentOS is deployed in my company in various ways. For example, I'd say we're a consulting company, which means we've probably already had all possible scenarios somewhere, and Docker on CentOS is simply part of everyday life, no matter where.

I wouldn't say there's a particular cloud provider that I prefer or frequently use for Docker on CentOS. Of course, the three big ones—AWS, Azure, and GCP—all offer it. There are also smaller, especially European providers. I wouldn't really say that we particularly prefer one or that I personally prefer one; instead, what matters is what the customer already has and what makes sense overall.

If a customer or someone were to ask me which one they should use if they don't have anything in use yet, I would base that on additional criteria. I would never choose a specific cloud just because I prefer the Docker on CentOS system there the best. There's much more to it than that.

My advice to others who want to use Docker on CentOS is to learn Docker on CentOS, try it out, and try to go into depth as early as possible. That means I've set up a container and you'll normally notice pretty quickly that the container is running as root, which is dangerous, and secondly that an image is very large.

The root problem is easy to solve. Making the image smaller then already requires a trick or two. I would say spend time with it, because if you learn Docker on CentOS well, you also learn something about Linux systems to some extent. It's fun, but in my opinion you should really do it via the command line and less via graphical tools.

Graphical tools are nice later to keep a certain overview, but building containers, setting them up, operating them, and learning how they work—that should all be done via the command line.

I mainly use Docker on CentOS on my NAS, and on my NAS I use it to deploy several different applications, such as monitoring how my NAS is running, handling downloads, and monitoring my NAS.

Docker on CentOS has had a positive impact on my organization by making it possible to save time and improve security. I can back up all the data quite easily and redeploy it on another machine or on the same machine in case of a crash.

Let's say it hasn't yet happened that I needed to restore the data, but in any case, I've done the backups, and so if it ever had to happen, I would be ready.

The best features offered by Docker on CentOS are that it's rather easy to set up. Docker is quite easy to set up, pretty simple to restart, and when I need to create new use cases, it's pretty simple to set up, stop, restart, and update.

Among all these features, the fact that I can set it up easily seems the most valuable in my daily work. For example, with simple YAML code, it's pretty easy to do, rather quick, and rather secure.

I don't know how Docker on CentOS could be improved at this point. I think it's already very good as it is, and they should just continue along the same path. I don't see any areas for improvement.

I've been using this solution for about three years.

Docker on CentOS is very stable in my daily use.

The scalability of Docker on CentOS is good.

I haven't had to contact customer support for Docker on CentOS so far.

I was not using another solution before.

Docker on CentOS is deployed in my organization locally, on-premises.

I have not observed a return on investment in terms of time or money saved, or other measurable benefits from this tool.

Since I use Docker on CentOS locally, it's free, so there's no cost issue regarding price, installation costs, and license management.

I did not evaluate other options before choosing Docker on CentOS.

My advice to other people who are considering using Docker on CentOS is that it's a very good solution. I would rate this product nine out of ten.

My main use case for Docker on CentOS is economizing. First, we were having to spin up a PBX mainly, and when using Asterisk, instead of creating a full dedicated server for this, I would use Docker to spin up the Asterisk that then easily integrates the Asterisk user cases, especially a customer calling us with our Django and API. Docker containers allow us to match the incoming call with the record so that we know who is calling us, at what time, and using which phone number so that we can create an omnichannel.

Using Docker on CentOS has specifically helped me manage incoming calls and match records through ease of scalability and ease of troubleshooting. In terms of reliability and vertical or horizontal scaling, it is much easier when using containers, and making changes that are specific to a certain element is easier than bringing down the whole infrastructure, so I find that troubleshooting failure is also easier.

Docker on CentOS has positively impacted my organization by saving time and reducing costs in terms of manpower. We do not require as many engineers because Docker gives you infrastructure as code through our cloud platform. Now that you can easily maintain infrastructure as code, you find that you do not need maybe ten plus engineers to manage complex platforms across multiple markets.

The time to recover was almost cut in half when we started simplifying this using microservices. We noticed that we can do a lot more in terms of reporting because databases would be quite heavier in production and impact bare metal VMs. This vertical and horizontal scale that is automated helped us, and even when someone is running a report, there is business continuity. We saw that the incidents that were raised because of lack of system resources during heavy reporting was almost cut by half, moving from thirteen incidents to only one incident a week.

Going from thirteen incidents a week down to one was mainly due to going the microservices way, and then also splitting the underlying workload, splitting more of a reporting workload from live platforms.

To improve Docker on CentOS, apart from having CentOS be end of life, which raises a security risk, I do not see anything else that I can point out about Docker. The only reason for sometimes the build cache surprises of Docker and volume permission headaches, especially on Linux, are considerations. We were finding a way of managing the image bloat on Docker.

I have been using Docker on CentOS for the last seven to eight years.

Docker on CentOS is very much stable.

The scalability of Docker on CentOS, while I note that we are moving away from CentOS if not already, I would give it a ten out of ten in terms of scalability and ease of management of the libraries.

For customer support for Docker on CentOS, I do not reach out. We always use the community of Docker and the Linux community or the CentOS community, which gives reliable information. Professional support is not needed since everything we do is in-house.

Before Docker on CentOS, we were using VMs entirely and bare metals. When we switched to microservices, it is quite much better in terms of scaling and horizontal and vertical scaling.

My experience with pricing, setup cost, and licensing is that since we do it in-house, apart from paying for the cloud hosting, there is nothing like an associated cost with that.

Before choosing Docker on CentOS, we did not evaluate any other options. The solution was just to move to microservices using Docker.

I am migrating workloads from CentOS to another Linux flavor. Regarding the libraries and the security aspect, nothing to add apart from that it is end of life and I am quite behind schedule of migrating these workloads away from CentOS. I would trust the repository updates from CentOS, given that most of these would be tested before they are taken to Red Hat. Apart from the migration from end of life, there is a huge risk that I am seeing, but there is nothing else I can add.

Regarding Docker on CentOS's AI capabilities, I cannot provide expertise as I am not a security expert. I trust the updates from the Docker repository and everything that has been updated, and I would say that I trust the platform as Docker.

My advice to others looking into using Docker on CentOS is that since Docker is still supported and growing and the community is good, it is a great product. For CentOS, either move to Rocky Linux or move to Debian.

I rate Docker on CentOS an eight out of ten.