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
Cannot connect to desktop VSCode, ENAMETOOLONG #1045
Comments
Hi @m2Giles thanks for reporting is VSCode installed as rpm or flatpak? |
Just tried with both a flatpak and code installed in distrobox and both worked for me I'm on OpenSUSE Aeon, not bluefin, but that should not be impactful |
It only appears to fail on the first run when it uses the vscode URL. After the fail, I can connect to Devpod from VScode. Browser vscode always seems to work. VScode installed via rpm on host. I haven't tried the flatpak yet. Docker and Podman were both showing the same behavior. Should I remove ~/.devpod and rebuild? |
Try with either vscode flatpak and/or code in distrobox and let's see 👍 |
Hey, I don't believe in bluefin it can be uninstalled from rpm easily to then try the flatpack (unless we have both the flatpack and rpm?). It's an OCI limitation. Because of how OCI layers work, everything stays in the image and if it is removed it is basically just dereferenced in later layer in which it is removed. |
I decided to install the flatpak (so I have both rpm install and flatpak install on my system now). It seems devpod opened in the flatpak version, so that's good. However, upon connecting, rather than getting enametoolong, I just get this:
Like the other user mentioned, VSCode on browser works fine. By the way, this resolves the issue if it helps with debugging possibly, however its needed almost anytime devpod is opened then: ublue-os/bluefin#892 (comment) |
What happened?
When attempting to connect to desktop vscode, receive an error that ENAMETOOLONG
What did you expect to happen instead?
Connection
How can we reproduce the bug? (as minimally and precisely as possible)
On both docker and podman on a local host. Spin up any devpod. For example https://github.com/ublue-os/bluefin
My
devcontainer.json
:Local Environment:
DevPod Provider:
Anything else we need to know?
Image:
When connecting from vscode instead of launching from devpod, vscode can connect.
The text was updated successfully, but these errors were encountered: