-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Teleport 8.0 commands fail on CentOS 7 #9028
Comments
I am also seeing this |
Same here... |
Another issue that is kinda linked to this one is the fact that the deb repository only offer the 8.0 version as of today.
Edit: This was already reported that it's an issue #8166 |
Our Ubuntu 18.04 base image contains a version of glibc that is too new for Centos 7. As a result, our builds contain a runtime dependency on this new version and will not run on Centos 7. This commit leverages multi stage builds to build the Rust static libraries on a Centos 7 box. These binaries are copied into a special directory in the buildbox image, which make will look for. In addition: - Configure Cargo to generate dep-info paths relative to the teleport directory. https://doc.rust-lang.org/cargo/guide/build-cache.html#dep-info-files - Leverage these dep info files to so that make is smart enough to run Cargo only if there have been changes to the Rust code. Fixes #9028
In the meantime, the CentOS 6 binaries should work: https://get.gravitational.com/teleport-v8.0.0-linux-amd64-centos6-bin.tar.gz |
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
Customers who have opted to use rpm packages over binary installs are having to spend time creating their own rpms . For consistency with previous releases it would be good to include rpms to accompany any tar releases. |
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
The issue isn't really fixed yet. |
Wait, how would you get centos binaries to even install on a Debian based system? |
@SMillerDev You cannot. But this issue isn't linked directly to CentOS. You can also replicate this issue on some Debian version which are bundled with an old version of GLIBC. |
Correct, the only thing specific about CentOS with this issue is that CentOS ships with an old version of GLIBC. Perhaps a more appropriate name for the CentOS binaries would be "Teleport - old GLIBC" or something. In any case, users who wish to run Teleport on systems with such an old version of GLIBC will be now be able to use these binaries when they ship. |
Would it be possible to add a libc version requirement to the .deb so that system which aren't compatible won't update using the deb repo ? |
Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028
That seems like a reasonable request to me. Would you mind creating a separate issue so this discussion doesn't get lost in an old closed issue? |
* Expose endpoint for fetching single desktop (#9041) * updates endpoints * Exposes an endpoint for fetching a single desktop by name * Apply suggestions from code review Co-authored-by: Zac Bergquist <[email protected]> * changes inaccurate desktopUUID to desktopName Co-authored-by: Zac Bergquist <[email protected]> * docs: LDAP service account setup (#8875) * updating docs with service account tutorial * minor corrections * Apply suggestions from code review Co-authored-by: Zac Bergquist <[email protected]> * wording changes based on CR * minor changes and fixes and adds updated photos with new naming convention * Updating documentation * updating gpo instructions to actually make sense * nits * adding instructions for exporting ca * removing unhelpful screen shot * Fixes quotes and updates to LDAPS Co-authored-by: Ben Arent <[email protected]> * clarifying comment Co-authored-by: Zac Bergquist <[email protected]> Co-authored-by: Ben Arent <[email protected]> * Enhance LDAP desktop discovery (#9152) * Refactor component heartbeat callbacks Consolidate the OK/degraded broadcasts so the same logic isn't duplicated for each component. * Periodically update discovered desktops Fixes #8644 * Allow customizing the desktop search With this change, we support a discovery base DN other than '*', and add support for further filtering the results with additional LDAP filters. Additionally, we filter out group managed service accounts, which show up in LDAP searches for (objectClass=computer), despite not being comptuers. (This is mostly harmless, as the service accounts aren't present in DNS, so Teleport just ignores them. It does, however, log a DNS error message that could be confusing, so we explicitly filter these out just to be safe. This was discovered when testing on AWS managed AD, which creates a gMSA for DNS. * simplify connection establishment (#9098) * Adds username and initial screen size to the websocket parameter string and sends over tdp during the connection process * simplifications from CR * fixes // // * Update e ref * Create separate builds for CentOS7 (+fips) Add new buildboxes for centos7 and centos7-fips. For now, we will continue to support both CentOS 6 and 7. Eventually we will drop support for CentOS 6, and the only supported CentOS builds will be these new CentOS 7 builds. Fixes #9028 * [auto] Update webassets in zmb3/desktop-access-backports (#9210) 444cf33 simplify connection establishment (#480) gravitational/webapps@444cf33 [source: -w teleport-v8] [target: -t zmb3/desktop-access-backports] Co-authored-by: Isaiah Becker-Mayer <[email protected]> Co-authored-by: Ben Arent <[email protected]>
@zmb3 when will these fixed releases show up in the RPM repo? |
AFAIK there are currently no plans to create separate CentOS 6/7 RPMs - the binary tarballs for those distributions should be used instead. There is a separate issue tracking adding a glibc dependency to avoid installing the current DEB/RPM files on systems which cannot support them: #9247 |
That should probably be noted in the install instructions because https://goteleport.com/docs/installation/ seems to suggest to use the yum repo (which works as long as you don't install 8.x releases) |
Agree with @SMillerDev. Another suggestion would be to have different yum repos for different major versions, so that one could upgrade major version, once you had tested on a test/dev machine. |
Description
What happened:
After updating to Teleport 8.0 on CentOS 7 Teleport fails to start.
What you expected to happen:
Teleport to start as it did with 7.x.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
Server Details
teleport version
): 8.0.0-1/etc/os-release
): CentOS 7Client Details
tsh version
): Teleport v7.3.3 git: go1.17.2Debug Logs
Please include or attach debug logs, when appropriate. Obfuscate sensitive information!
teleport --debug
)tsh --debug
)The text was updated successfully, but these errors were encountered: