-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
us-east-2 #1
Comments
It looks like 2.42.0 was the version pinned, and 2.43.0 would have been new enough to support us-east-2 I'm updating the tags in teamhephy/boto and will adjust this dockerfile so we can try a build next |
Actually it looks like that pinned commit never made it into deis/boto, which as 2.42.0 as the latest tag I'm looking inside of registry:v2.4.2 and registry:git-8d66318 which is newer, both seem to have 2.43.0 and so should probably already support us-east-2 Will confirm again with the reporter that registry is at v2.4.2 in case this diagnosis is in error... I'm grepping in /usr/lib/python3.5/site-packages/boto of that image and finding all kinds of us-east-2 mentions though, so this may be a bad report. |
Can we verify that this is not an issue or do we need to look into this more? |
I still need to look into this. The reporter confirmed he is running all of the latest registry and builder images on his cluster, but still can't operate buckets in us-east-2 – so it seems likely that there is an issue here. |
It's been reported that registry and builder are missing support for the Ohio AWS region
https://github.com/deis/registry/blob/d3c2b63cb2c219fc7c89df5ada762a16f27eeba7/rootfs/Dockerfile
This pinned version seems to be the culprit, someone is going to have to upgrade boto to fix this. Cross-posting in builder since reporter indicated that both are affected.
The text was updated successfully, but these errors were encountered: