Skip to main content

Configure local yum on docker container

Configure local yum on docker container.
Below are the simple steps to configure local yum using RHEL8 iso in docker container-
Step 1 - Mount your ISO on your (Docker)local system
[root@server109 ~]# mkdir /iso
[root@server109 ~]# mount -o loop /RHEL-8-0-0-BaseOS-x86_64.iso /iso
[root@server109 ~]#

 Step 2 - Launch a container
[root@server109 _data]# docker container run -dit --name yum -v /run/media/root/RHEL-8-0-0-BaseOS-x86_64/:/iso  centos:7
a3483d2b718f339f6c3e9a4600e27e61086af512ef6bca67fcc1b73ada70838c

-dit - Tags(Detach, Interactive, Terminal )
--name yum - Name of container
-v /run/media/root/RHEL-8-0-0-BaseOS-x86_64/:/iso - /iso here dvd will bind on container
centos:7 - Name of container image:version

Step 3 - Attach container
[root@server109 _data]# docker container attach yum
[root@a3483d2b718f /]# cd /iso/
[root@a3483d2b718f iso]# ls
AppStream  BaseOS  EFI  EULA  GPL  RPM-GPG-KEY-redhat-beta  RPM-GPG-KEY-redhat-release  TRANS.TBL  extra_files.json  images  isolinux  media.repo

RPM packages are available under AppStream  and BaseOS directories, now we can configure yum very easily. Before that let's check how many packages are available from by default yum configuration -
[root@872e373dcd53 /]# yum repolist |grep repolist
repolist: 12225

Step 4 - Configure local yum
[root@a3483d2b718f iso]# cd /etc/yum.repos.d/
[root@a3483d2b718f yum.repos.d]# ls
CentOS-Base.repo  CentOS-CR.repo  CentOS-Debuginfo.repo  CentOS-Media.repo  CentOS-Sources.repo  CentOS-Vault.repo  CentOS-fasttrack.repo
[root@a3483d2b718f yum.repos.d]# rm -rf  *.repo
[root@a3483d2b718f yum.repos.d]# ls
[root@a3483d2b718f yum.repos.d]#
[root@a3483d2b718f yum.repos.d]# vi myyum.repo
[dvd]
name = dvd1
baseurl=file:///iso/AppStream
gpgcheck=0

[dvd]
name = dvd2
baseurl=file:///iso/BaseOS
gpgcheck=0
[root@a3483d2b718f yum.repos.d]# yum repolist |grep repolist
repolist: 6647

That's all, your local yum has been configured!!

Labels

Labels:

Comments

Post a Comment

Please share your experience.....

Popular posts from this blog

error: db5 error(11) from dbenv->open: Resource temporarily unavailable

If rpm command is not working in your system and it is giving an error message( error: db5 error(11) from dbenv->open: Resource temporarily unavailable ). What is the root cause of this issue? How to fix this issue?   just a single command- [root@localhost rpm]# rpm --rebuilddb Detailed error message- [root@localhost rpm]# rpm -q firefox ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db5 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm ^Cerror: db5 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages database in /var/lib/rpm package firefox is not installed [root@localhost rpm]# RPM manage a database in which it store all information related to packages installed in our system. /var/lib/rpm, this is directory where this information is available. [root@localhost rpm]# cd /var/lib/rpm ...
2 comments
Read more

Failed to get D-Bus connection: Operation not permitted

" Failed to get D-Bus connection: Operation not permitted " - systemctl command is not working in Docker container. If systemctl command is not working in your container and giving subjected error message then simple solution of this error is, create container with -- privileged option and also provide init file full path  /usr/sbin/init [root@server109 ~]# docker container run -dit --privileged --name systemctl_not_working_centos1 centos:7 /usr/sbin/init For detailed explanation and understanding I am writing more about it, please have look below. If we have a daemon based program(httpd, sshd, jenkins, docker etc.) running inside a container and we would like to start/stop or check status of daemon inside docker then it becomes difficult for us to perform such operations , because by default systemctl and service  commands don't work inside docker. Normally we run below commands to check services status in Linux systems. [root@server109 ~]# systemctl status ...
4 comments
Read more

call to function "map" failed: the "map" function was deprecated in Terrafrom

How to change map method to tomap method? Let's say you have multiple tags in your code which was written quite back and that time it was working fine on old Terraform version before v0.12 but if the same code you execute on updated/latest Terrafrom you get subjected error while try to run Terrafrom plan command. Then this article will help you to fix your issue. What is simple solution to fix this issue? Just replace " map " method to " tomap " and just to little bit formatting for the same. Syntax:- map ({"Name", "My_Name"), map("AppName", "My_App")}) tomap ({"Name"  =   "My_Name",  "App_Name"  =   "My_App"}) or tomap ({     "Name"  =   "My_Name",     "App_Name"  =   "My_App" }) #Code with " map " method resource "aws_instance" "My_instance"   ami   =   my_ami   instance_type =   my_type   tags  =   merge(var.tag...
1 comment
Read more