-
Notifications
You must be signed in to change notification settings - Fork 313
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
Builds are failing with "Could not build wheels for cryptography" #956
Comments
This seems like it might be a python 2.7 issue. It looks like the build failed when attempting to build "wheel for cryptography" using python 2.7 even though python 2.7 support was removed in PR #922.
I'm wondering if this might have something to do with the docker image |
Python 2.7 support was removed from `cloudreach/sceptre-circleci` docker image in commit Sceptre/sceptre-circleci@975fa09 and tagged with https://github.com/Sceptre/sceptre-circleci/releases/tag/v0.5.0 We removed python 2.7 support from sceptre in PR Sceptre#922 however we neglected to update cicleci to build with the updated docker image. This PR will update the docker image to remove python 2.7 from the builds.
updating docker container in PR #959 didn't fix the built, although i think it's the correct thing to do. I'm wondering if updating to a newer version of alpine might help since it will get a newer version of openssl ? https://github.com/Sceptre/sceptre-circleci/blob/master/Dockerfile#L1 |
I believe I've figure this out. The build is failing because the sceptre build is setup to use the Sceptre/sceptre-circleci docker container with alpine ver 3.7. I've verified that updating Alpine to ver 3.11 will allow the sceptre build to work without error. The fix is to update Alpine to ver 3.11 in Sceptre/sceptre-circleci and then use that in the Sceptre/sceptre build. That fix is in the following PRs: Sceptre/sceptre-circleci#1 and #959 |
It looks like the sceptre-circleci build is failing due to a permissions issue.
|
@ngfgrant it looks like CircleCI is failing on the initial checkout w/ an invalid SSH key. Perhaps whatever SSH key was originally setup so that CircleCI could clone https://github.com/Sceptre/sceptre-circleci has been changed? Is there any chance you (or someone w/ admin access to the sceptre-circleci GH and Circle projects) could sort this out soon? I'd like to try working on fixing #942, but will need CI running. |
…fix build (Sceptre#959) * [Resolves Sceptre#956] Fix sceptre build Python 2.7 support was removed from `cloudreach/sceptre-circleci` docker image in commit Sceptre/sceptre-circleci@975fa09 and tagged with https://github.com/Sceptre/sceptre-circleci/releases/tag/v0.5.0 We removed python 2.7 support from sceptre in PR Sceptre#922 however we neglected to update cicleci to build with the updated docker image. This PR will update the docker image to remove python 2.7 from the builds. * update pip * fix pip flag * adjust updated version with PR sceptre-circleci/pull/1
Attempt to fix build failure `error: can't find Rust compiler`. The docs says try to update pip.. https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-with-error-can-not-find-rust-compiler`
build has been fixed. |
The circleci builds have been failing for the past week.. https://app.circleci.com/pipelines/github/Sceptre/sceptre
The text was updated successfully, but these errors were encountered: