see explanation below.
Explanation
/etc/init.d/iptables start
iptables -F
iptables -X
iptables -Z
/etc/init.d/iptables save
chkconfig iptables on

See the solution below in Explanation.
Explanation:
Solution:
Create the Quadlet file:
mkdir -p /etc/containers/systemd
cat > /etc/containers/systemd/sleepy.container < < 'EOF'
[Container]
Image=registry.access.redhat.com/ubi10/ubi
ContainerName=sleepy
Exec=sleep 3600
[Install]
WantedBy=multi-user.target
EOF
Reload and enable:
systemctl daemon-reload
systemctl enable --now sleepy.service
systemctl status sleepy.service
Detailed Explanation:
* Quadlet is the preferred modern way to manage Podman containers with systemd for new configurations.
* The .container file is translated into a systemd-managed service.
* RHEL 10 documentation notes that podman generate systemd still exists, but Quadlets are preferred for new setups. ( Red Hat Documentation )

* [root@node2 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vdb 252:16 0 5G 0 disk
└─vdb1 252:17 0 4.2G 0 part
└─vgrz-lvrz 253:2 0 4.1G 0 lvm /datarz
vdc 252:32 0 5G 0 disk
vdd 252:48 0 5G 0 disk
vde 252:64 0 10G 0 disk
[root@node2 ~]# parted /dev/vdc mklabel msdos
[root@node2 ~]# parted /dev/vdc mkpart primary 1MiB 4200MiB
[root@node2 ~]# parted /dev/vdc set 1 lvm on
* [root@node2 ~]# udevadm settle
[root@node2 ~]# pvcreate /dev/vdc1
Physical volume "/dev/vdc1" successfully created.
[root@node2 ~]# vgcreate -s 16M datavg /dev/vdc1
Volume group "datavg" successfully created
[root@node2 ~]# lvcreate -n datalv -L 4000M datavg
Logical volume "datalv" created.
[root@node2 ~]# mkfs.xfs /dev/datavg/datalv
[root@node2 ~]# mkdir /data
[root@node2 ~]# blkid
/dev/mapper/datavg-datalv: UUID="7397a292-d67d-4632-941e-382e2bd922ce" BLOCK_SIZE="512" TYPE="xfs"
* [root@node2 ~]# vim /etc/fstab
UUID=7397a292-d67d-4632-941e-382e2bd922ce /data xfs defaults 0 0
[root@node2 ~]# mount UUID=7397a292-d67d-4632-941e-382e2bd922ce /data
[root@node2 ~]# reboot
[root@node2 ~]# df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/datavg-datalv xfs 3.9G 61M 3.9G 2% /data

[root@node2 ~]# lsblk
[root@node2 ~]# fdisk /dev/vdb
Welcome to fdisk (util-linux 2.37.4).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
This disk is currently in use - repartitioning is probably a bad idea.
It's recommended to umount all file systems, and swapoff all swap
partitions on this disk.
Command (m for help): n
Partition number (3-128, default 3):
First sector (1476608-10485726, default 1476608):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (1476608-10485726, default 10485726): +512M
Created a new partition 3 of type 'Linux filesystem' and of size 512 MiB.
Command (m for help): w
The partition table has been altered.
Syncing disks.
[root@node2 ~]# mkswap /dev/vdb3
[root@node2 ~]# vim /etc/fstab
/dev/vdb3 swap swap defaults 0 0
[root@node2 ~]# swapon -a
[root@node2 ~]# swapon
NAME TYPE SIZE USED PRIO
/dev/vdb2 partition 243M 0B -2
/dev/vdb3 partition 512M 0B -3

system-config-authentication
LDAP Server: ldap//instructor.example.com (In domain form, not write IP) OR
# yum groupinstall directory-client (1.krb5-workstation 2.pam-krb5 3.sssd)
# system-config-authentication
1.User Account Database: LDAP
2.LDAP Search Base DN: dc=example,dc=com
3.LDAP Server: ldap://instructor.example.com (In domain form, not write IP) 4.Download CA Certificate
5.Authentication Method: LDAP password
6.Apply
getent passwd ldapuser40