We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
VS Code then warns me "You are about to connect to an OS version that is unsupported by Visual Studio Code." and includes a "Learn More" button referencing https://code.visualstudio.com/docs/remote/faq#_can-i-run-vs-code-server-on-older-linux-distributions
It seems that foundationdb/devel:centos7-latest is too old and will stop working in 6 months (February 2025):
foundationdb/.devcontainer/devcontainer.json
Line 3 in 48064f6
The text was updated successfully, but these errors were encountered:
Specifically, the supported OS conditions that VS Code cares about are "glibc >= 2.28 and libstdc++ >= 3.4.25".
Sorry, something went wrong.
Related: FoundationDB/fdb-build-support#25
Looks like the Docker file is ready https://github.com/FoundationDB/fdb-build-support/blob/main/docker/rockylinux9/Dockerfile. However, we haven't published the image to Docker Hub yet. I'll discuss with @xis19 about it.
Hello,
We encounter the same issue than other regarding the obsolescence of the glibc (quite hard to properly upgrade it from the centos7:latest image).
Do you know when the image release is planned @xis19 .
Let's target the image release before EOY.
No branches or pull requests
VS Code then warns me "You are about to connect to an OS version that is unsupported by Visual Studio Code." and includes a "Learn More" button referencing https://code.visualstudio.com/docs/remote/faq#_can-i-run-vs-code-server-on-older-linux-distributions
It seems that foundationdb/devel:centos7-latest is too old and will stop working in 6 months (February 2025):
foundationdb/.devcontainer/devcontainer.json
Line 3 in 48064f6
The text was updated successfully, but these errors were encountered: