[ECS/Fargate] [request]: ECS Exec : support readonlyRootFilesystem containers
<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** I would like to use the ECS Exec feature with readonlyRootFilesystem enabled containers. **Which service(s) is this request for?** ECS/Fargate **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Currently readonlyRootFilesystem enabled containers are not supported, the AWS managed agent crash soon after launch. **Are you currently working around this issue?** Yes. I've managed to get it working with `readonlyRootFilesystem: true` by mounting `/managed-agents`, `/var/lib/amazon/ssm` and `/var/log/amazon/ssm` as
Posted by sd65 on Apr 30, 2021, 5:29 PM
Tags
Related issues
- [BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
- Feature Request: Auto-resume CLI session when usage limit resets
- Please deobfuscate the Python
- [Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
- # 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
- [FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
reliability (Software)
[BUG] Cowork (Windows): all Plan9 shares fail with "Plan9 mount failed: invalid argument" after Windows update KB5124008 (26200.9445) — uninstalling the KB fixe
Feature Request: Auto-resume CLI session when usage limit resets
Please deobfuscate the Python
[Bug] MLX version of Gemma 4 26B fails to load: "Model type gemma4 not supported" (macOS)
# 233 Developers Discussed Abandoning the Office Add-in Platform — An Open Letter on the Office.js Stability, Security & Trust Crisis
[FEATURE] Allow users to configure which shell the Bash tool uses or inherit initial shell
Admin Materials and Surfaces
AMD Support
[ECS/Fargate] [request]: ECS Exec : support readonlyRootFilesystem containers
<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** I would like to use the ECS Exec feature with readonlyRootFilesystem enabled containers. **Which service(s) is this request for?** ECS/Fargate **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** Currently readonlyRootFilesystem enabled containers are not supported, the AWS managed agent crash soon after launch. **Are you currently working around this issue?** Yes. I've managed to get it working with `readonlyRootFilesystem: true` by mounting `/managed-agents`, `/var/lib/amazon/ssm` and `/var/log/amazon/ssm` as
Comments (0)
No comments yet. Start the discussion.