cancel
Showing results for 
Search instead for 
Did you mean: 
MSCHMEL
Flight Engineer
Flight Engineer
  • 404 Views

Reasons for not being able to open a remote shell

Jump to solution

Hello everyone,

can you tell me under which circumstances it is not possible to connect to a running container using rsh? I recently had that problem. Unfortunately, I cannot remember the exact error message. Can a container be configured in a way to just refuse rsh connections?

Thanks and kind regards,

Matthias

Labels (1)
1 Solution

Accepted Solutions
MSCHMEL
Flight Engineer
Flight Engineer
  • 342 Views

Thank you. Next time I have that problem I will make sure to take note of the error message.

View solution in original post

Tags (5)
2 Replies
Chetan_Tiwary_
Community Manager
Community Manager
  • 374 Views

Hard to tell without looking at the error and configuration. But there could be a bug with the image as well eg docker exec or oc rsh does not work with registry.access.redhat.com/rhel7:7.3  but it works with registry.access.redhat.com/rhel7:7.4 onwards.

Or if there is a pod disruption budget error and you cant evict unhealthy pods, so doing rsh to one of the pods will fail.

Or may be the command was wrong.

 

Tags (5)
MSCHMEL
Flight Engineer
Flight Engineer
  • 343 Views

Thank you. Next time I have that problem I will make sure to take note of the error message.

Tags (5)
Join the discussion
You must log in to join this conversation.