• 2,079 Views

How to Downaload rsyslog image throgh podman (RHCSA )

Jump to solution

In RHCSA i am unable to download the rsyslog image using url http://registry.example.com after sucessfully login to registry

Can anyone guide me where i missed it

I PASS the exam with score 255 but will gain more 30+ marks for container question

 

Labels (1)
1 Solution

Accepted Solutions
HeshD
Cadet
Cadet
  • 1,981 Views

1. install neccessary packages

2. configure registry.conf to with url

3. login to registrey

4. search the image name / inspect image

5. pull image

If you need exact commands to be execute, let me know.

View solution in original post

10 Replies
HeshD
Cadet
Cadet
  • 1,982 Views

1. install neccessary packages

2. configure registry.conf to with url

3. login to registrey

4. search the image name / inspect image

5. pull image

If you need exact commands to be execute, let me know.

Emana
Cadet
Cadet
  • 1,207 Views

Thanks for your help sir. In my case, the registry was preconfigured. I actually logged in, search and saw the image but i tried all these and non of them worked:

#podman pull rhel8/rsyslog-custom-cert
0 Kudos
  • 942 Views

I had the same problem, registry was preconfigured but I wasn't able to pull image, it worked when I used sudo, I think link from below might be a solution - you can not manage containers after logging with su, if you want to use ssh it must be ssh session of "podman_user"
https://www.redhat.com/sysadmin/sudo-rootless-podman

0 Kudos
perezcab
Cadet
Cadet
  • 489 Views
Is correct..! You must login with ssh. If you login with su - you have somes problems with the env., And can't set the systemd.
0 Kudos
perezcab
Cadet
Cadet
  • 488 Views
Try with podman search rsyslog...
0 Kudos
Nath
Cadet
Cadet
  • 1,691 Views

Hello all, I had the same problem.

The pull command simply dont work. It always gave some sort of error (don't remember it exactly).

I also tried to login to the registry using GUI and used the path mentioned in the text box (instruction on pulling the image), that didn't work either. The instructiion was for "docker pull", but Indeed I replaced docker with podman, but the image wont simply download, no matter how many times I tried.

I am seriously thinking there is something wrong with the connectivity n pulling procedure or firewall/permission etc (I am not skilled in configuring n managing registries - so not able to deduce what cud hv gone wrong)

I am almost sure I was doing the right procedure - I may be wrong. Can someone please help if anyone was able to pull the image?

0 Kudos
Emana
Cadet
Cadet
  • 1,209 Views

I had the exact same problem today.

0 Kudos
  • 1,019 Views

Hi all, I have a question with regards to rsysyslog-custom-cert on RHCSA exam. During the exam, I have successfully configured the container for rootless service and persistent storage. It was running but somehow it did not start up after reboot. I have followed the steps that I have learned from Red Hat online learning. Did I miss out anything? Do I need to register something, etc?

0 Kudos
Robert_Bryant
Mission Specialist
Mission Specialist
  • 924 Views

After you set everything up, if you don't ssh log in as the user the container runs under, it won't be running. Only for the user that created it/ persisted it. So if you checked as root, you wouldn't see it with podman ps -a

Also, sorry if this is included in what you're referring to in terms of "steps that I have learned..." but did you remember to do all of these steps after getting the container running? :

mkdir -p /home/containeruser/.config/systemd/user

cd /home/containeruser/.config/systemd/user  (podman has to generate systemd svcs here)

podman generate systemd --new --files --name rsyslog-custom-cert

podman stop rsyslog-custom-cert

podman rm rsyslog-custom-cert

systemctl --user daemon-reload

systemctl --user enable --now container-rsyslog-custom-cert

(verify running with podman ps or systemctl --user status container-rsyslog-custom-cert)

loginctl enable-linger

(and verify that linger is enabled with)

loginctl show-user containeruser 

0 Kudos
Join the discussion
You must log in to join this conversation.