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

CTFE GLIBC Error #1118

Closed
myatsko-1 opened this issue Aug 2, 2023 · 4 comments · Fixed by #1119
Closed

CTFE GLIBC Error #1118

myatsko-1 opened this issue Aug 2, 2023 · 4 comments · Fixed by #1119
Assignees

Comments

@myatsko-1
Copy link

I'm trying the Docker deployment on a Amazon Linux server. When I run docker-compose --profile frontend up, it successfully launches the ctfe-db, ctfe-trillian-log-server-1, and ctfe-trillian-log-signer-1 containers. But, I keep getting 'exited with code 1' when it tries to launch the ctfe-ctfe-1 container:

ctfe-ctfe-1 | /ct_server: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by /ct_server) ctfe-ctfe-1 | /ct_server: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by /ct_server)

Any ideas how to get past this error?

@roger2hk roger2hk self-assigned this Aug 2, 2023
@roger2hk
Copy link
Contributor

roger2hk commented Aug 2, 2023

This issue is very likely related to golang/go#57328.

@roger2hk
Copy link
Contributor

roger2hk commented Aug 2, 2023

@myatsko-1 Please try again. The latest ctfe Docker image in gcr.io/trillian-opensource-ci/ctfe should have this issue fixed.

@myatsko-1
Copy link
Author

myatsko-1 commented Aug 2, 2023 via email

@roger2hk
Copy link
Contributor

roger2hk commented Aug 2, 2023

I'm glad that the fix resolved your issue. I found some other issues with the instructions when I tried to replicate this issue. Please feel free to submit new issues or pull requests to update the deployment documentation.

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

Successfully merging a pull request may close this issue.

2 participants