ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I am pretty new to this Docker world and I am trying to deploy an image (nodejs-typescript service) from aws ECR to aws ECS but when I create the service inside the cluster this error appears and the taks never gets running: exec /usr/local/bin/docker-entrypoint.sh: exec format error My Dockerfile looks like this: FROM node:lts-alpine WORKDIR /usr/app COPY p
Asked · Dec 6
answered · Dec 8
I'd like to use IMDSv2 inside a container running on an EC2 instance. I want to use the tokens because they are required in my metadata options: metadata_options { http_tokens = "required" http_endpoint = "enabled" } Calling the API from the EC2 instance returns my token as expected. curl -s -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-meta
I am running a Docker image on an ECS cluster to shell into it and run some simple tests. However when I run this: aws ecs execute-command \ --cluster MyEcsCluster \ --task $ECS_TASK_ARN \ --container MainContainer \ --command "/bin/bash" \ --interactive I get the error: The Session Manager plugin was installed successfully. Use the AWS CLI to start a sessio
I am totally new to AWS but I've been running my dockerized application locally for months now with no issues. Now that I am trying to deploy this app via AWS ECS/Fargate, my containers are stopped repeatedly with this linux error: standard_init_linux.go:219: exec user process caused: exec format error . This error seems to suggest that the architecture in F
Slightly tearing my hair out with this one... I am trying to run a Docker image on Fargate in a VPC in a Public subnet. When I run this as a Task I get: ResourceInitializationError: unable to pull secrets or registry auth: pull command failed: : signal: killed If I run the Task in a Private subnet, through a NAT, it works. It also works if I run it in a Publ
With the recent release of Docker Images for Lambda functions, I've decided to try out this functionality using CloudFormation . So, the lambda below considers a docker image stored in Elastic Container Registry , with permissions to access the image following the examples in the documentation . AWSTemplateFormatVersion: '2010-09-09' Transform: AWS::Serverle
docker