Similar to the instanceRole problem with database, registry doesn't seem to like instanceRoles
- Dominant language
- Go
- Stars
- 16
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Similar to the instanceRole problem with database, registry doesn't seem to like AWS instanceRoles. The create_bucket script was failing with the empty creds. Maybe the real issue is the env is set when it shouldn't be.
Watching this possible upstream problem:
https://github.com/docker/distribution-library-image/issues/47
ECS also uses instanceRoles for their "tasks".
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is identified. Start by reproducing the create_bucket failure with empty credentials, inspect how the environment is populated for AWS instance roles, and compare the behavior with the linked upstream issue. Done means the expected instance-role credential behavior is established and the registry failure has a confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, go
- Domain
- authentication, backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100