Skip to content
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

Don't rely on governmentpaas/awscli to build octodns container #217

Closed
wants to merge 1 commit into from

Conversation

Krenair
Copy link
Contributor

@Krenair Krenair commented Nov 24, 2020

Since boto/boto3#2596, we can't just pip3 install
boto3 on top of it. The image we use comes from this PaaS repository:
https://github.com/alphagov/paas-docker-cloudfoundry-tools/blob/main/awscli/Dockerfile
which pins awscli to 1.17.2. This commit uses 1.18.140 which shouldn't have the issue.

Also, use curl-ssl from GHCR instead of DockerHub.

Since boto/boto3#2596, we can't just pip3 install
boto3 on top of it. The image we use comes from this PaaS repository:
https://github.com/alphagov/paas-docker-cloudfoundry-tools/blob/main/awscli/Dockerfile
which pins awscli to 1.17.2. This commit uses 1.18.140 which shouldn't have the issue.

Also, use curl-ssl from GHCR instead of DockerHub.
@Krenair
Copy link
Contributor Author

Krenair commented Nov 24, 2020

We might want to do alphagov/paas-docker-cloudfoundry-tools#202 instead if we can.

@Krenair Krenair closed this Nov 25, 2020
@Krenair Krenair deleted the octodns-paas-awscli branch November 25, 2020 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant