-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Internal error when running ExecuteCommand #6070
Comments
Hi @WhyNotHugo, sorry to hear you're having trouble. To best determine what the issue could be, please use our template when opening up a new issue, as it contains the information that could be useful. I see you've provided the architecture and CLI version, but having the full command and debug logs will be needed to assist you further. Thanks! Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug SDK version number Platform/OS/Hardware/Device To Reproduce (observed behavior) Expected behavior Logs/output Additional context |
Sure! Keep in mind that you can add Describe the bug SDK version number
Platform/OS/Hardware/Device
To Reproduce (observed behavior) Run Expected behavior It should open an interactive session. Actual behaviour
Logs/output
Additional context The only difference I'm seeing between tasks that fail and tasks that don't is the Sorry if I messed up the formatting, it seems that GitHub strips formatting when copy-pasting for some reason. |
Thanks for providing the details, @WhyNotHugo! I found this thread on the AWS Containers Roadmap repository of users running into this problem: See here specifically:
Otherwise we may need to get you in touch with AWS support to determine more completely what the issue could be. Having the request ID from your response will be helpful (it's Separately, I'm not sure why you didn't get prompted with an issue template! Ours live here, and we disabled the ability to open an issue without a template. If you can let me know how you got in that state it would help me improve the developer experience here! |
Those comments indicate that their issue lied elsewhere (missing IAM role). Like I said, if I turn off |
Oh, that issue does point to aws-containers/amazon-ecs-exec-checker#21, which also mentions my problem. It would seem (so far), that it's an issue with the current implementation on the AWS side. |
Thanks for finding that @WhyNotHugo - I think I can close this in lieu of that issue: |
|
I almost always get this error when attempting to use
ExecuteCommand
:It would seem that it does not occur when attempting to
ExecuteCommand
on containers with a read-write root filesystem. Is is possible that it always fails with a read-only root?Let me know if there's any additional information that might be useful.
The text was updated successfully, but these errors were encountered: