Closed siourdas-vasilis closed 2 years ago
The issue was that I missed the external : true
attribute in secrets group. Closing this.
Maybe the docs needs an update on the x-aws-keys
part that they miss the external option.
https://docs.docker.com/cloud/ecs-integration/#secrets
BUG REPORT INFORMATION
Description
I am using docker compose with ECS integration. I am trying to apply the feature of reading secrets from AWS SecretsManager to my containers. I tried running
matomo:latest
andmetabase/metabase
images unsuccessfully.Steps to reproduce the issue:
secrets: my_aws_secret: name: ${AWS_SECRETS_ARN} x-aws-keys:
docker context create ecs aws docker context use aws docker compose up
Results I received:
When I run
docker compose up
I got the following error:where mypath is my current working directory containing the docker-compose.yml file.
Also Github Actions fails silently on docker compose up, giving:
Error: Process completed with exit code 14.
and no more info.Results I expected: Docker compose up , to run successfully and deploy the container in ECS, with the secrets specified.
Additional important information :
When I remove the all the secret related attributes, docker compose up works!
Output of
docker compose version
:Output of
docker info
:Additional environment details: Working on WSL v2