MSCHMEL

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2024
02:00 PM
- 1,037 Views
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
1 Solution
Accepted Solutions
MSCHMEL

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2024
09:49 AM
- 975 Views
2 Replies

Community Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2024
11:21 PM
- 1,007 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.
MSCHMEL

Flight Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2024
09:49 AM
- 977 Views
Join the discussion
You must log in to join this conversation.