URL: https://rol.redhat.com/rol/app/courses/rh134-8.2/pages/ch13s13
Reporter RHNID: ssanyal@redhat.com
Section: 3 - Lab: Running Containers
Language: en-US (English)||||||||
Workaround:

Description: an explanation is requested for the below by external learner : 

"Description: problem with skopeo inspect after su - user
It is not possilel to erch the image with the scope, after the su - . in the lab, the only way to do it is to logind directly top the certain user ssh user@server. Please compare : https://rol.redhat.com/rol/app/courses/rh134-8.2/pages/ch13s13"

learner understand the concepts under 

https://rol.redhat.com/rol/app/courses/rh134-8.2/pages/ch13s11 ( lecture section ) , as applicable to podsvc user and using a user account for creation of a service, but wants to know why under ch13s13, step 2 , the skopeo comand always fails when doing a su - instead of a ssh. **

step 2.2 specifically requests the user to "Use the ssh command to log in to serverb as the podsvc user."
The user clearly understand that the purpose is to create a container from a user account.
however, we notice that the skopeo command will fail , if , instead of ssh , a sudo is done to podsvc user.

it passes when doing a ssh to podsvc@serverb - as expected 

why does it fail when using a su - podsvc on serverb ?