roll arm32 builds back to alpine 3.12 to avoid time64 change #130
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
|
I'm happy to apply the py3-cryptography change to the other Dockerfiles, if that would be preferable. |
|
I am a bot, here are the test results for this PR: |
|
The issue I was having with building py cryptography must be something with my build system, as I had the same issue with alpine 3.13, and I see the weekly Jenkins build finished yesterday without issue. Also, this may soon be redundant, as I appear to have fixed the time64 issue upstream. I submitted a pull request here. I have done some basic testing on Ubuntu 20.04 amd64 and Alpine 3.13 amd64 and armhf, and the issue seems to be resolved with no obvious bugs. |
|
You are hitting the libseccomp error that has been an issue with focal on Ubuntu and on alpine after they started using 64bit time. So the best option is to update libseccomp or update to a 64bit OS. |
|
|
Just downgrading the buildstage should suffice. |
capntrips
force-pushed
the
arm32v7-3.12-build
branch
from
892a49d
to
6e875f7
Compare
|
I am a bot, here are the test results for this PR: |
Description:
Rolled buildstage back to alpine 3.12
Reverted #125 and installed py3-cryptography alpine package to avoid rust-lang/cargo#9187
Benefits of this PR and context:
Fixes #127 and potentially #124
How Has This Been Tested?
Deployed to Raspberry Pi 4 and tested basic functionality (download, check, repair, extract).
Source / References:
musl time64 Release Notes