-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Re-add support for amazonlinux:1, centos:7, and ubuntu:14.04 #13183
Comments
IMHO, there is still many centos 7 servers alive. |
Is this targetting any release at the moment? I was looking if this another issue was already merged in a new version to update my vector node and just saw that version Building from source on a CentOS 7 machine works as a workaround? |
Hi @leandrojmp ! Unfortunately we haven't been able to fix this quite yet. However, yes, building on a CentOS 7 machine should work to create a binary linked against the older version of libc. |
If this doesn't have a milestone anymore, maybe at least update the documentation to say that CentOS 7 isn't supported? https://vector.dev/docs/setup/installation/operating-systems/centos/ |
@abh I agree with that. at least need documentation update |
Looks like cross-rs got a special target |
…eenable centos7 and others. Fixes vectordotdev#13183
I have added PR that addresses this issue. I see @bruceg assigned this to himself, I hope we didn't do the work in parallel now :) |
…eenable centos7 and others. Fixes vectordotdev#13183
…eenable centos7 and others. Fixes vectordotdev#13183
…eenable centos7 and others. Fixes vectordotdev#13183
Thanks for taking this up @apollo13. I had taken a look at it before @flyingflo pointed out that |
Can we get a patch release for this? |
0.27.0 will be going out in a week and a half so I think we'll likely just loop it into that release. |
The newer cross images build on Ubuntu 16.04 which ends up linking against a newer libc and libc++ than is available on ubuntu:14.04, centos:7, amazonlinux:1. We dropped the release tests for them in #13146 to unblock the nightly build, but we should explore re-adding them by linking against older versions of libc/libc++ since these OS's are not yet EOL.
The text was updated successfully, but these errors were encountered: