No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U02GCR8KHL4> what Docker registry are you logged in to?
```docker info | grep Registry```

you might consider setting the image explicitly:

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecr/#RepositoryImage>

do you have any env vars set?
```env | grep -i AWS```

Yes `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY` in `.env`

And I’m not quite sure how to set the image explicitly

you'd need to define an explicit repo, then pass it as an arg:

<https://github.com/pulumi/pulumi-awsx/blob/333b1ff0d649e3f19187c2e8edc292dd6c131fbd/nodejs/awsx/ecr/repository.ts#L77>

But when I run
```const repository = new awsx.ecr.Repository("app")```
to create a repo, it’s also in the wrong account

Do you have any idea why it’s grabbing the wrong aws account even when the local .env file has the right aws account credentials (and `aws configure` also has the right account credentials)?

I would hazard a big guess that it's an issue locally, I've never seen this bug before. Not discounting that it's a bug, but it's very unlikely

I'm assuming

`aws sts get-caller-identity` from the CLI returns the correct account?

does your stack configuration have any `aws:` variables set?

Yes to both: `aws sts get-caller-identity` returns the correct account and I have one `aws:` variable (`aws:region`) set

Is there any way to debug this? I’m just not sure how to go about fixing this

Preferably I’d like to understand why this is happening - I would’ve assumed that Pulumi simply takes my local AWS credentials (from `aws configure` or .env) and uses that to authenticate for aws services like ecr?

Or is it doing something else underneath?

This is interesting - I deleted and created a new project and it works now

Is there anything that gets saved with projects other than the Pulumi.yaml files?

yes, the stack configuration: `Pulumi.stack.yaml`