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

build 2.5.1 with Alpine 3.6 due to sidekick Segfaults #233

Closed
shleeable opened this issue Sep 17, 2018 · 2 comments
Closed

build 2.5.1 with Alpine 3.6 due to sidekick Segfaults #233

shleeable opened this issue Sep 17, 2018 · 2 comments

Comments

@shleeable
Copy link
Contributor

Hello,

Mastodon is built with sidekick and we're recently committed from ruby2.4.4-alpine3.6 to ruby2.5.1-alpine3.7... but have had to revert due to segfaults with sidekick.

We've planning to diagnose the root cause of these faults and would like to test with different version of alpine.

Thanks.

@shleeable
Copy link
Contributor Author

mastodon/mastodon#8712

@shleeable shleeable changed the title build 2.5.1 with Alpine 3.6/3.8 due to sidekick Segfaults build 2.5.1 with Alpine 3.6 due to sidekick Segfaults Sep 17, 2018
@tianon
Copy link
Member

tianon commented Sep 17, 2018

Mirroring my comment from #235:

I'm not sure how I feel about adding a new variant based on Alpine 3.6 (especially as we're trying to move forward into Alpine 3.8 to replace 3.7 by default) -- I think the release last week (for the apk security fix) was more the exception than the norm, and that Alpine 3.6's ship has really sailed generally except for severe security vulnerabilities.

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

No branches or pull requests

2 participants