Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to create execute session with task that has multiple containers #2518

Open
EranPercepto opened this issue Jan 13, 2025 · 0 comments
Open

Comments

@EranPercepto
Copy link

Hello,

Issue description: Im unable to create sessions or exec in different containers on the same task (even after terminating the session with the other container).

Issue replication: Let's say I have 2 containers (A and B) running on the same task. When I create an exec session with Container A, I can login to with out any issue and I do log out (I can see the session terminated message) from the session. Now If i try to login to a different container (say B) this time - I'm getting the below mentioned error, and we can see the same phenomenon if I do login to Container B first and terminate the session and try to login to Container A

"The Session Manager plugin was installed successfully. Use the AWS CLI to start a session.
An error occurred (TargetNotConnectedException) when calling the ExecuteCommand operation: The execute command failed due to an internal error. Try again later."

Thanks.
Eran Ovadia.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant