Podman 101: Practical Labs

-
    podman logo

 What is Podman? Podman is a daemonless container engine for developing, managing, and running OCI Containers on your Linux System.

 Example:
 1- Deploy Apache web server on podman:
 2- Create volume persistent and join  with podman.
 3- Test web server access.
 4- Change index.html and reload podman
 5- Test changed.
6-  use  podman as system services.

 

[root@podman ~]#   mkdir -p /opt/var/www/html



 [root@podman ~]#  cd /opt/var/www/html



 [root@podman html]# wget --page-requisites --convert-links https://registry.fedoraproject.org/



 [root@podman html]# chown 1001 -R /opt/var



 [root@podman ~]#   mkdir -p /opt/var/www/html
 Create podman with local volume persistent:

[root@podman html]#  podman run -d --name myhttpservice -p 8080:8080 -v                               /opt/var/www/html:/var/www/html:Z    registry.fedoraproject.org/f29/httpd



[root@podman html]#  podman   logs  -f   myhttpservice



172.250.1.32 - - [18/Sep/2019:11:06:36 +0000] "GET /registry.fedoraproject.org/ HTTP/1.1" 200 164657 "-" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"



172.250.1.32 - - [18/Sep/2019:11:06:36 +0000] "GET /registry.fedoraproject.org/css/styles.css HTTP/1.1" 200 5735 "http://172.250.1.157:8080/registry.fedoraproject.org/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"



172.250.1.32 - - [18/Sep/2019:11:06:36 +0000] "GET /registry.fedoraproject.org/fedora.png HTTP/1.1" 200 6265 "http://172.250.1.157:8080/registry.fedoraproject.org/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"



172.250.1.32 - - [18/Sep/2019:11:06:37 +0000] "GET /registry.fedoraproject.org/js/scripts.js HTTP/1.1" 200 3132 "http://172.250.1.157:8080/registry.fedoraproject.org/" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"



172.250.1.32 - - [18/Sep/2019:11:06:37 +0000] "GET /registry.fedoraproject.org/css/search.svg HTTP/1.1" 200 1321 "http://172.250.1.157:8080/registry.fedoraproject.org/css/styles.css" "Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36"


 Open http://localhost:8080/registry.fedoraproject.org in your Web Browser:

Change index.html:




 EXAMPLE: System Services in Containers:

 Why not use container as system services:

 

[root@Podman ~]#  vi /etc/systemd/system/myhttpservice.service



-----



[Unit]



Description=Just and http service with Podman Container



[Service]



Type=simple



TimeoutStartSec=30s



ExecStartPre=-/usr/bin/podman rm "myhttpservice"



ExecStart=/usr/bin/podman run --name myhttpservice -p 8080:8080 -v /opt/var/www/html:/var/www/html:Z registry.fedoraproject.org/f29/httpd



ExecReload=-/usr/bin/podman stop "myhttpservice"



ExecReload=-/usr/bin/podman rm "myhttpservice"



ExecStop=-/usr/bin/podman stop "myhttpservice"



Restart=always



RestartSec=30



[Install]



WantedBy=multi-user.target



-------- 




[root@Podman ~]#  systemctl daemon-reload



[root@Podman ~]#  systemctl status myhttpservice.service



 myhttpservice.service - Just and http service with Podman Container



   Loaded: loaded (/etc/systemd/system/myhttpservice.service; disabled; vendor preset: disabled)



   Active: inactive (dead)




[root@Podman ~]#  systemctl start myhttpservice.service



[root@Podman ~]#  systemctl status myhttpservice.service



myhttpservice.service - Just and http service with Podman Container



   Loaded: loaded (/etc/systemd/system/myhttpservice.service; disabled; vendor preset: disabled)



   Active: activating (auto-restart) (Result: exit-code) since Sun 2019-09-22 10:16:04 EET; 15s ago



  Process: 8140 ExecStart=/usr/bin/podman run --name myhttpservice -p 8080:8080 -v /opt/var/www/html:/var/www/html:Z registry.fedora>



  Process: 8114 ExecStartPre=/usr/bin/podman rm myhttpservice (code=exited, status=125)



 Main PID: 8140 (code=exited, status=125)

### Open http://localhost:8080/registry.fedoraproject.org in your Web Browser

------------------------------------------------------------------------------------
Good Luck https://www.linkedin.com/in/ahmedms/

Comments

Post a Comment

Popular posts from this blog

Kubernetes 104: Create a 2-node k3s cluster with k3sup

-
Image
Create a 2-node k3s cluster with k3sup Kubenetes-Master   = 192.168.17.5 Kubenetes-Worker  = 192.168.17.6 k3sup machine        = 192.168.1.131 !!!  Allow ssh access between k3sup  & two nodes of kubernetes       and between two nodes of kubernetes. !!!  Install K3SUP: [root@devops ~]# curl -sLSf https://get.k3sup.dev | sh which: no k3sup in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) x86_64 Downloading package https://github.com/alexellis/k3sup/releases/download/0.3.0/k3sup as /tmp/k3sup Download complete. Running as root - Attempting to move k3sup to /usr/local/bin New version of k3sup installed to /usr/local/bin _ _____ | | _|___ / ___ _ _ _ __ | |/ / |_ \/ __| | | | '_ \ | < ___) \__ \ |_| | |_) | |_|\_\____/|___/\__,_| .__/ |_| Version: 0.3.0 Git Commit: 7d954414def98c52ae1f6de08ac5317e4260e673 [root@devops ~]# !!! Install kubernetes master: [root@devops ~]# export SERVE
Read more

Cisco Nexus: Configuration VXLAN.

-
Image
Configuration VXLAN on Cisco Nexus !!! First: Legacy Method: Connect between two servers by Trunk VLAN: Second: VXLAN Method: Connect between two servers by VXLAN Tunnel. First Method:          NXOS-L:  vlan 2  interface Ethernet1/2     switchport access vlan 2     spanning-tree port type edge     no shutdown interface Ethernet1/1    switchport mode trunk    spanning-tree port type network    no shutdown NXOS-R: vlan 2 interface Ethernet1/2    switchport access vlan 2    spanning-tree port type edge    no shutdown interface Ethernet1/1    switchport mode trunk    spanning-tree port type network    no shutdown  Result: ------------------------------------------------------------------------------------------------- Second Method: VXLAN !! NXOS-L: feature ospf  interface Ethernet1/1     no switchport     ip address 10.3.4.3/24     ip router ospf 1 area 0.0.0.0     ip ospf network point-to
Read more

How to configure OSPF on Palo Alto Networks Firewall?

-
Image
How to configure OSPF on Palo Alto Networks Firewall !! Steps: 1- Create Virtual Router. 2- Create three Zones (Site A – Site B – Site C). 3- Create security rule allow (ping) between Site A & Site C. 4- Create OSPF routing protocol on two firewalls. -------------------------------------------------------------------------------------------                                                                     PaloAlto - 1 1- Create Virtual Router (VR-1) PaloAlto-1 2- Create Zones PaloAlto-1: 3- Assign Interfaces PaloAlto-1: 4- Create rule allow (ping) and deny other 5- Apply OSPF between two interfaces (eth ½ - eth 1/1) Show routing table on Palo-Alto-1: ====================================================================                                                                PaloAlto - 2 1- Create Virtual Router (VR-1) PaloAlto-2 2- Create Zones PaloAlto-2: 3- Assign Interfac
Read more