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
In our organization we use a NFS based file system to house our HOME directories, which can be accessed from machines of different architectures. The current directory structure used by open-remote-ssh places the node executable in the ~/.vscodium-server/bin/<commit>/ directory, which prevents the HOME directory of a given user from being utilized by machines of different architectures. For example, my first use of the open-remote-ssh extension from the workstation where I have VSCodium installed was to connect to a x86_64 machine, which then installed the vscodium-server binaries into the aforementioned location in my network-based HOME directory. If I try connecting to a SSH Target of a different architecture (e.g., aarch64 or ppc64le) the server installation script fails, saying Server script already installed in <location>, followed by Error server did not start sucessfully (sic) because the existing binary is not correct for that architecture. The server installation script needs to append an architecture value (derived from uname -m) to the installation directory so that binaries from multiple architectures can be installed simultaneously.
The text was updated successfully, but these errors were encountered:
In our organization we use a NFS based file system to house our HOME directories, which can be accessed from machines of different architectures. The current directory structure used by
open-remote-ssh
places thenode
executable in the~/.vscodium-server/bin/<commit>/
directory, which prevents the HOME directory of a given user from being utilized by machines of different architectures. For example, my first use of theopen-remote-ssh
extension from the workstation where I haveVSCodium
installed was to connect to ax86_64
machine, which then installed thevscodium-server
binaries into the aforementioned location in my network-based HOME directory. If I try connecting to a SSH Target of a different architecture (e.g.,aarch64
orppc64le
) the server installation script fails, sayingServer script already installed in <location>
, followed byError server did not start sucessfully
(sic) because the existing binary is not correct for that architecture. The server installation script needs to append an architecture value (derived fromuname -m
) to the installation directory so that binaries from multiple architectures can be installed simultaneously.The text was updated successfully, but these errors were encountered: