https://dagster.io/ logo
Join Slack
Powered by
there is a credential issue when using aws sso log...
# ask-community
k
there is a credential issue when using aws sso login , its looking for the ~/.aws/credentials path
d
Hi Koby - could you share more about where exactly you're seeing this error? Do you have a full stack you could share?
k
there is no full stack trace only the go error
d
Could you give me a set of steps I could follow to reproduce the error myself?
k
sure, let me check my history
setup:
Copy code
git clone <https://github.com/dagster-io/dagster.git>
cd dagster/examples/deploy_ecs
docker context create ecs dagster-ecs
# interactive >> select an existing aws profile (default)
then: input
Copy code
docker --context dagster-ecs compose --project-name dagster up
output:
Copy code
NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
we are using aws sso login for credentials
made sure i am logged in and that ecs context is present 
in docker context ls
d
got it, this is very helpful context, thanks! cc @jordan who knows more of the ins and outs of ECS. I'm not actually sure if this error message is specific to dagster or not, but he may be
j
Does 
aws sts get-caller-identity
return the IAM user/role you expect? What versions of the aws sdk and docker compose are you running?
Copy code
aws --version
docker compose version
k
Copy code
docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019
sts caller identity is right
aws version
aws-cli/2.2.7 Python/3.8.8 Linux/5.13.19-200.fc34.x86_64 exe/x86_64.fedora.34 prompt/off
j
what about 
docker compose version
(not 
docker-compose version
- the ecs deployment docs use the new compose v2 https://docs.docker.com/compose/cli-command/#compose-v2-and-the-new-docker-compose-command)
iirc the ecs context isn’t available with docker-compose but perhaps they’ve backported it since I last looked
k
that might be the issue, looks like the docker compose command doesnt exist
weird that i got this far without it
was sure i installed it
j
yeah - the cutover from 
docker-compose
to 
docker compose
seems very confusing to me. https://docs.docker.com/cloud/ecs-integration/#prerequisites try these - either by installing docker desktop or using the standalone script that installs 
docker compose
k
i use linux, dont have that privilage
looks like the installation didnt work
meh 😕
j
https://docs.docker.com/cloud/ecs-integration/#install-script this script in particular didn’t work?
k
You already have the Docker Compose CLI installed, overriding with latest version
i bet its a docker plugin path definition thing
j
this is all vaguely familiar from when i needed to get this installed on our buildkite boxes - let me see if i can dig up what i did to make that happen
k
Copy code
docker plugin enable compose
Error response from daemon: plugin "compose" not found
j
https://github.com/dagster-io/dagster/commit/a759b176e6babfc2aca0e407a25b7362e8b5b24c hm 🤔 I remember running into these exact issues with the install script but it looks like i didn’t leave myself any breadcrumbs for how i got around it. i’ll keep digging.
k
10x
92 Views
Open in Slack
PreviousNext
Powered by