Documentation at building_and_maintaining_your_rhel_ai_environment/setting_up_accounts (eg. https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_ai/1.4/html/building_and_maintaining_your_rhel_ai_environment/setting_up_accounts#setting_up_accounts ) is referencing use of sudo in the podman command and then copying auth.json from user of id 0.

This is not recommended and suboptimal for the current RHEL AI (from 1.4) deployments - the default case is a normal user account, or a env-specific "normal" account like cloud-user or azureuser. The following changes in the docs are desired:

rhc connect --organization <org id> --activation-key <created key>
^^ add sudo there as rhc command needs root privileges

sudo podman login registry.redhat.io

^^ remove sudo

cp run/containers/0/auth.json /etc/ostree/

^^ add sudo and change the user id, so the command is: 

sudo cp /run/user/1000/containers/auth.json /etc/ostree/

(and maybe leave a note that the original command should be used if the deployment is configured to run as root user)