You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue occur when all extensions are disabled?: N/A (REH does not start regardless of the extensions in REH, but Open Remote extension is needed on the host to get REH running)
VS Code Version: Code OSS 1.83.1 on the host, OpenVSCode Server 1.83.0 in container (it worked without issues in 1.78).
OS Version: Alpine Edge x86_64.
Steps to Reproduce:
Try to use Remote SSH extension on host to connect into Alpine-based container (on the latest edge, with the latest gcompat v1.0.0-r4 installed), configuring extension to use https://github.com/gitpod-io/openvscode-server/ for REH binaries;
Observe that REH binary (openvscode-server) won't start, with "fcntl64: symbol not found" error message.
This is probably related to VSCodium/vscodium#1634 ; apparently this has already been fixed in VSCodium 1.82, but is still an issue in OpenVSCode Server.
Does this issue occur when all extensions are disabled?: N/A (REH does not start regardless of the extensions in REH, but Open Remote extension is needed on the host to get REH running)
Steps to Reproduce:
openvscode-server
) won't start, with "fcntl64: symbol not found" error message.This is probably related to VSCodium/vscodium#1634 ; apparently this has already been fixed in VSCodium 1.82, but is still an issue in OpenVSCode Server.
There is a working workaround: manually replacing node binary in openvscode directory in container with the one downloaded from https://unofficial-builds.nodejs.org/download/release/v18.15.0/node-v18.15.0-linux-x64-musl.tar.xz , as suggested in VSCodium issue discussion, fixes this issue.
The text was updated successfully, but these errors were encountered: