By using AWS re:Post, you agree to the Terms of Use


AWS container services offer the broadest choice of services to run your containers and run on the best global infrastructure, with 77 Availability Zones across 24 regions. AWS also provides strong security isolation between your containers, ensures you are running the latest security updates, and gives you the ability to set granular access permissions for every container.

Recent questions

see all

Exec linux command inside a container

Hi team, I connected to my envoy container using this command : ``` aws ecs execute-command --cluster cluster-name --task task-id --container container-name --interactive --command "/bin/sh" ``` once inside the container I'm trying to execute this Linux command: ` ps aux` I have this error : `sh: ps: command not found` the version of the distribution inside the envoy container is " ``` Linux version 4.14.276-211.499.amzn2.x86_64 (mockbuild@ip-xx-x-xx-225) (gcc version 7.3.1 20180712 (Red Hat 7.3.1-13) (GCC)) #1 SMP Wed Apr 27 21:08:48 UTC 2022 ``` I tried to install ps : `yum install -y procps` I have this error : ``` Loaded plugins: ovl, priorities Could not retrieve mirrorlist error was 14: curl#56 - "Recv failure: Connection reset by peer" One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: amzn2-core/2/x86_64 ``` is there a way to run basic commands inside the envoy container like ps, map...? Thank you.
asked 7 days ago

Popular users

see all

Learn AWS faster by following popular topics