-
Notifications
You must be signed in to change notification settings - Fork 5
v2.7.0 might break backups #8
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
Comments
I had issues but I was testing against the new S3_ENDPOINT config that hasn't been merged yet, speaking to Digital Ocean Spaces S3 API. It seems likely that S3's region certificate authorities signing certs are bundled in the boto2 package. Then, if that's true, there might be no issues with AWS when the new base image does not include Let's be sure before we publish v2.20 and unleash the hordes on it, is all! Thanks |
Not sure how to best test this for all platform. I have only tested in AWS and have not tested the backup process.
Are you sure this is the case @kingdonb ? I checked the Docker image build logs from yesterday of the new postgres image and I see that the |
From the logs of the docker image build:
This is in Step #4 of the Dockerfile. |
OK, that is great news, it was missing when I tested it. Looks like someone has fixed it already. I'll close this issue, but it would be good to test all three environments. That was the missing part, as whatever commit I was building from was missing |
Before the new workflow release is cut, I just wanted to confirm that someone has tested Postgres and confirmed that backups work with the new postgres:11 image backing this new release.
Environments to test:
Please report which builds you've tested and I will update the list in this issue (or you can)
The text was updated successfully, but these errors were encountered: