Mission Specialist
Mission Specialist

RHCSA EX200 v8k Exam experience

Hi Everyone,

i attempted the RHCSA v8k (EX200) exam and passed luckily, but still doubtful about the container question, which was very simple. 

i tried but command was not succesful, and not even on my laptop VMs (RHEL8.0 and 8.2),  but i tried the same successfully on RHEL 8.4, 8.6 and even on RHEL9.

so , still confused why this happened, is it a bug or wrong underline platfrom to test the exam objective.


Rehmat Ali

Labels (3)
Tags (3)
0 Kudos
4 Replies
Flight Engineer
Flight Engineer

Hello, let us refrain from talking about exam content, but let us focus on the "podman"/"container" error you are facing, could you reproduce the error command on your local machine eg on Fedora/RHEL? If yes, what error is it? Are you sure you are not forget about SELINUX Context for the container folder (container_t)? and are you sure that you already map the subiud and subguid like on podman documentation?


I will remind again, let us talk about those, if you sure you can share more information regarding your problem, I will be happy to reply, as we all in RHCSA are bound by NDA, but here we can still talk about the exercise or the course content. Thanks.

Teaching RHEL Curicullum @ since 2019! Thanks for RH Academy !
0 Kudos
Mission Specialist
Mission Specialist

i have done these steps, and rootless container was not running after reboot.


# vi /etc/systemd/journal.conf --> (Storage=persistent)
$ sudo systemctl restart systemd-journald
# setsebool -P container_manage_cgroup on
$ mkdir /home/user1/container_journal
$ mkdir /home/user1/.config/systemd/user
$ chown -R user1:user1 /home/user1/.config
$ podman login
$ podman pull
$ cd /home/user1/.config/systemd/user
$ podman run -d --name logserver -v /home/user1/container_journal:/var/log/journal:Z rhel8/rsyslog
$ vi .bashrc
export XDG_RUNTIME_DIR=/run/user/$(id -u)
$ source .bashrc

$ podman generate systemd --files --name logserver
$ loginctl enable-linger user1
$ loginctl show-user user1
$ podman stop logserver (do not remove container)
$ systemctl --user daemon-reload
$ systemctl --user enable --now container-logserver.service
$ podman ps -a
$ sudo reboot
$ pdoman ps -

0 Kudos
Flight Engineer
Flight Engineer

Have you check the podman logs logserver?


2nd have you check systemctl --user status container-logserver.service?


there are another type of flags on podman generate systemd


Should be --new... you should check it.

Teaching RHEL Curicullum @ since 2019! Thanks for RH Academy !
Flight Engineer
Flight Engineer

Hello @RehmatAli !

I hope you're fine. 

Unfortunately, we cannot provide any assistance due to the NDA agreement. 

You can request an exam review by sending an email to If you have any concerns about your attempt.


Kind Regards, 



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