How to install Docker in Red Hat 8.0

[Denzil]

Good day to you,

may you be good  enough to walk me though for a Docket installation.

Kind Regards

[Denzil]

Hello @Chetan_Tiwary_ 

Thank you again.

By the way un relation to Cloud while most most of the serves are on Linux, how may you rate the industry and her demans againt Podman Vs. Docker?

Kind Regards,

Denzil

[Denzil]

Hello Again Travis,

Thanks a bunch for stepping in!!

As I stressed the reason why I have installed Linux in my laptop, in the world of Cloud so much is being talked and refferred to Docker. I was shocked and suprised to see the evelution and the relevation of Docker, et al. Hence the interest to install Docker too.

Taking your wonderful advise, I am keen to, if you may furnish me a link as to how to install Podman.

I I have taken your waring into account, over the issues I have with the subscriptions. I shall first fix this issue. By the way, yesterday it did ask me to re-register and I eecuited that step. It confirmed I have an active subscription. I left it there. I will see to this later in the evening or Thursday the 23rd of October 2025, morning.

Kind Regards,

Denzil

[Travis · Accepted solution]

@Denzil -

This is covered in some of our basic administration courses, but again, since it is part of RHEL ...

yum install podman

I know you want to learn cloud, but cloud is a "generic" term. I think in your instance what you might want to learn for cloud is "containers" which would be a generic term. 

The two basic Linux runtimes and management for containers are Docker and Podman. Both essentially do the same thing, but Docker has been around slightly longer. So sometimes when people are refering to using "Docker" and running a "Docker image" they often are referring to running a container image.

It would be like someone saying they run their service in the cloud on AWS, but that isn't actually where it is ... it might be Azure, Google Cloud, or somewhere else, but AWS is what they new the most about so instead of saying cloud, they say everything runs on AWS.

One of the things I did on some of my systems when Red Hat first switched to Podman was I had to make a command alias to where the docker command actually aliased Podman. I did that because 95% of everything in command syntax and 100% of the most common things for running containers is the same syntax, you just substitute the name of the command.

In my opinion, if you are wanting to learn containers for the cloud (which I think is your goal) Podman is the superior solution because it manages the pods (again a new term) which could be a group of containers and services and this is the magic behind Kubernetes and OpenShift and what easiliy allows your multi-container services to work.

One thing to keep in mind ... and I'm wearing the T-shirt today (actually) with the saying on it ... Containers are Linux. You will be best served to understand how to use Linux basics and fundamentals before running and building containers. It will make things much easier to understand and absorb. It is one thing to find an article and run XXX or YYY container for a reason, but if you want to learn, build, maintain, control, and administer container and truly understand a good foundation in Linux is what you need.

[Denzil]

Hello Travis,

I envy you being sincere personif my queries were picked up my some one else, I would have given up Linux! That is the truth.

In relation to your paragraph two and three, if that someone explied this to me the way you have, I would have not chased the "Cloud" 

As regards to you paragraph four, thanks a million for that valuable advise. I shall remember until I die!

Then, reference "In my opinion, if you are wanting to learn containers for the cloud (which I think is your goal).." , please if you have the time, read, https://www.linkedin.com/in/denzil-peiris-9b803924/  and https://www.linkedin.com/feed/update/urn:li:activity:7374860268478152704/

Having said that, I falied to realize the power of Linux, and why Linux is so demanding, when I was advised by my first Cloud guru, Eissa Abu Sherif, back in 2018/ 2019. He said learn Linux and since you are planning to settle in Germany, germany is a  big Linux Company. Ignoring this, I jumped into the deep ocean, AWS - SAA 03. Finally acheived in 04th of May 2025, prior to that, AWS CLF C02 on18th of December 2024. I have completed  approximately 70%,IaS , Terrafom. I have completed projects using Terrafom. then it came to Docker. 

IaS, Docker, Kubernetes, OpenShift et el.,  as to advised and explained me, I knew without Linux I am dead. In a view to get the root access I spent a wealth of time, few months  over YouTube, internet and some "educators". Then suddenly it hit me to check here.

You have rightfully advised me through your final paragraph! Indeed I have to master Linux, then automatically I will digest "Cloud". One other thing if the person whom I trusted and paid, stuck to his promise, I would not be here. 

If you have read the book by Jeffery Archer Kan and Abel, your advise is almost like the final chaper in this book. If some one had educeted and advised me like you have,  when I decided to learn "Cloud" my life woud have been "wunderbar" 

There is always a reason why things happen?

Kind Regards,

Denzil

[Denzil]

Hello Travis,

Thank you for yum install podman.

I hope this will not conflict withe my subscriptions? After carful checks, I realized that it was the Docker installation which I attempted was the root cause. It did not go through.

Kind Regards,

Denzil

[Travis · Accepted solution]

@Denzil -

One of the huge and main reasons I mentioned using Podman is it is a built-in component of RHEL. If you only have RHEL installed and no other channels and software, there will never be issues (***) with installing a RHEL package from BaseOS or Appstream. Once you start installing 3rd party software and EPEL, all bets are off as you can accidentally replace Red Hat software with a package of the same name and newer version. It will install dependencies because that is what RPMs do ... look for software needed and attempt to resolve. Now when you update RHEL with a yum update it tries to install new pacakges but you have some things from upstream and dependencies that get broken because a new package isn't released or you have a combination of RHEL and upstream packages that don't mix well. I'm not saying it can't be done, but you should do so with caution. When I was in consulting, I had a customer that subscribed to EPEL to install individual packages they needed (that's OK) but they left the system subscribed to all EPEL channels and did a yum update now because they were using RHEL and products like Satellite and OpenStack, versions of PIP and Python were replaced and upgraded with newer non-Red Hat versions and that broke things with the application because now we had newer versions of files, and no longer had the versions required to support the layered RHEL product as it was replaced accidentally by the upstream.

I had specifically advised against Docker installation beause of that is it will at times have external dependencies and could cause version and RPM conflicts with RHEL. Again, the podman installation will allow you to do whatever you want with the container and should be very safe and easy for you to install. If you want to play with the containers in Windows, you can also do that by installing Podman Desktop. 

https://podman-desktop.io/

https://developers.redhat.com/products/podman-desktop/overview?sc_cid=RHCTG0240000434049&gad_source=...

I will also leave you with this for your learning ...

I had mentioned Red Hat Developer network and the Red Hat Developer subscription. I'm once again recommending this as a wonderful free source of information, software, and learning. There are some "lessons" that will teach targetted items. It also allows you to download the RHEL versions for installation and gives you the free developer subscription entitlements. There are also often eBooks and blogs to help you learn things and cheatsheets available.

https://developers.redhat.com/learn/rhel

https://developers.redhat.com/topics/containers

Red Hat provides a ton of free resources, including books. I've given a link to the Podman book as well as a bunch of cheat sheets. These aren't meant to replace formal training or a complete book, but will be useful as reference materials for providing insight. I often provided these to students when I was teaching Red Hat courses and these should help you as you are learning (hopefully they can be used as references, refreshers, and guides).

Excellent Book on Podman: https://developers.redhat.com/e-books/podman-action

Cheat Sheets:

https://developers.redhat.com/cheat-sheets/linux-commands-cheat-sheet

https://developers.redhat.com/cheat-sheets/red-hat-enterprise-linux-in-wsl

https://developers.redhat.com/cheat-sheets/red-hat-enterprise-linux-10-cheat-sheet

https://developers.redhat.com/cheat-sheets/advanced-linux-commands

https://developers.redhat.com/cheat-sheets/podman-cheat-sheet

https://developers.redhat.com/cheat-sheets/red-hat-enterprise-linux-8

https://developers.redhat.com/cheat-sheets/bash-shell-cheat-sheet

https://developers.redhat.com/cheat-sheets/intermediate-linux-commands-cheat-sheet

https://developers.redhat.com/cheat-sheets/systemd-commands-cheat-sheet

https://developers.redhat.com/cheat-sheets/containers

[Denzil]

Hello Travis,

Thanks a lot for that wealth of information. At the moment I am adhering to your advise and I am not installing Docker. I have uninstaleld it and hence the updates went smooth! 

By the way I have Pyton installed. Should I uninstall it too, paving way to Podman? Or let it be there?

Out of the Linux book you had highly recommended, I maged to get a PDF for version 9. I this serves my purpose along with the links you have furnished me with.

Thank you for the huge advise you have me over your first paragraph.

Having saif that if as strongly advised by you, if Podman paves the way, then that is it.

In my serch, an euucator who trains on line sent me a quote for US $ 1,700.00 for Docker et el. If I was employed in Oman , I would have. But having a prayer answered, you have provided all the answers.

Kind Regards,

Denzil

[Travis · Accepted solution]

@Denzil -

Great to hear and I'm not too worried about Python. I used that as a practical example. The reason it caused more problems is our layered applications Red Hat Satellite, OpenStack, etc. have very strict requirements on supported versions and tools that build on that. You have a more plain installation and I doubt a ton of other Red Hat paid products. Python doesn't interact with Podman per-se, so I don't think you will have any issue. You will know once you do a yum install podman.

The final piece of information I will give you is that you can see which RPM a binary was installed from, so you can identify where and how Python was installed, but again, for you it shouldn't matter.

$ which LogViewer
/usr/bin/LogViewer

$ rpm -qf /usr/bin/LogViewer
LogViewer-4.0.5-0.x86_64

$ dnf info LogViewer-4.0.5-0.x86_64
Repositories loaded.
Installed packages
Name            : LogViewer
Epoch           : 0
Version         : 4.0.5
Release         : 0
Architecture    : x86_64
Installed size  : 72.1 MiB
Source          : LogViewer-4.0.5-0.src.rpm
From repository : copr:copr.fedorainfracloud.org:tmichett:LogViewer

$ dnf info LogViewer
Updating and loading repositories:
Repositories loaded.
Installed packages
Name            : LogViewer
Epoch           : 0
Version         : 4.0.5
Release         : 0
Architecture    : x86_64
Installed size  : 72.1 MiB
Source          : LogViewer-4.0.5-0.src.rpm
From repository : copr:copr.fedorainfracloud.org:tmichett:LogViewer

This can give you an idea of how a binary file got installed, which RPM installed it, and then using DNF or YUM, it will give you the repostory that has the file available. Using that information but substituting with Python or Python3 (whatever you use as your Python command) will help you determine where this stuff came from, so that is the last piece of information I can provide to help you with your questions.

[Denzil]

Good day to you Travis,

Thank you and appreciate for that advise.

Indeed I have a very basic Red Hat Linux installation.

I am getting this response;  no LogViewer in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin), when I used 

$ which LogViewer

However based on your advise, I ran, yum install Podman.

Installed:
conmon-3:2.1.10-1.module+el8.10.0+23498+f7d19d48.x86_64 container-selinux-2:2.229.0-2.module+el8.10.0+23498+f7d19d48.noarch
containers-common-2:1-82.module+el8.10.0+23498+f7d19d48.x86_64 criu-3.18-5.module+el8.10.0+23498+f7d19d48.x86_64
fuse-overlayfs-1.13-1.module+el8.10.0+23498+f7d19d48.x86_64 fuse3-3.3.0-19.el8.x86_64
fuse3-libs-3.3.0-19.el8.x86_64 libnet-1.1.6-15.el8.x86_64
libslirp-4.4.0-2.module+el8.10.0+23498+f7d19d48.x86_64 podman-4:4.9.4-23.module+el8.10.0+23498+f7d19d48.x86_64
podman-catatonit-4:4.9.4-23.module+el8.10.0+23498+f7d19d48.x86_64 podman-gvproxy-4:4.9.4-23.module+el8.10.0+23498+f7d19d48.x86_64
podman-plugins-4:4.9.4-23.module+el8.10.0+23498+f7d19d48.x86_64 runc-1:1.1.12-6.module+el8.10.0+23498+f7d19d48.x86_64
shadow-utils-subid-2:4.6-22.el8.x86_64 slirp4netns-1.2.3-1.module+el8.10.0+23498+f7d19d48.x86_64

I beleive it went though successfully.

Kind Regards,

Denzil

Kind Regards,

Denzil

[Travis]

@Denzil -

I wasn't meaning you try the LogViewer. That is a custom log viewing applicaiton I made and it is on Fedora. The reason I used it is because it is coming from COPR which is another repository that might be like EPEL or something else and not from the regular Fedora repos or RHEL repos. 

I knew it was my application that was installed on my system from my COPR repository. The commands can be used and I had mentioned to you python.

The which is for any binary command you can type and it gives you the path. Once you have the PATH, you use the RPM command to see which RPM it came from, and then you can use the dnf/yum command to see which repository it comes from and how it was installed.