Closed gaby closed 3 years ago
Happy to make a bigger jump.
I don't believe Alpine flaws are exploitable in a normal Scope situation, but I recognize that folks run tools which highlight them.
@bboreham Great, changes have been made. Alpine now points to 3.13
Looks like the build fails now, you might try adding libpcap-dev
?
Also, the old Dockerfile was specific about MAJOR
.MINOR
.Patch
, let's keep that property... would you change the form of the FROM line from 3.13
back to 3.13.2
that mentions the more specific latest release available at this time?
Test still failing, I will take a look again tonight. The integration test for alpine 3.11.8 also failed, so it must be something else missing.
@bboreham @kingdonb I tried debugging this, but I can't figure out why it fails. PR #3834 is also failing with the same error.
The integration tests basically don't run at all for 3rd-party forks, due to mining. #2192
I have pushed your branch as 1st-party, so now the tests will re-run and hopefully succeed.
I apoologise the error message is very hard to understand; it would be better to fail the job straight off if it doesn't have secrets.
@bboreham, do you have any plans to official 1.13.2 release with the latest changes? Including new alpine?
Update alpine 3.11 to latest patch version.
It would make more sense at this point to update to 3.13, let me know if you want make to make the change.
Change log for 3.11.8: https://alpinelinux.org/posts/Alpine-3.10.6-3.11.8-3.12.4-released.html