patchelf VS vscode-remote-release

I mean, we don't have to hack the elf loader if we just rewrite every elf binary using patchelf: https://github.com/NixOS/patchelf

The parent commenter is already suggesting "just run a regex", so it seems like a trivial extension to their simple solution to "just run patchelf on every binary on your system"

Patching paths in text files typically used substituteInPlace (including in cowsay). For dynamic libraries, patchelf is typically used.

Install patchelf.

Thank you! I followed the instruction here, but it looks like I didn't actually install it, because my pacman -Q patchelf did not find anything. Maybe I was missing a dependency. Also, it was late so I didn't pay attention to warnings at the time.

How does an article on NixOS talk about the `rpath` issue without also mentioning the `patchelf` utility that NixOS developers created to solve this issue? It's a small tool that lets you modify ELF executables and binaries. It's also the recommended way for NixOS users to modify binaries to work properly.

https://github.com/NixOS/patchelf

So install it? https://github.com/NixOS/patchelf

NixOS doesn't have stable paths to shared libraries like macOS or other linux distributions (and this is the core feature) and always need to patch elf for current paths ( https://github.com/NixOS/patchelf ).

It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373

The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).

Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375

If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964

VSCode with Remote-Container extension installed.

Possibly related github issue?

This might be it.

Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238