Skip to content
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

Enabling wayland for VScode crash the extension #57

Open
jbtrystram opened this issue May 27, 2024 · 0 comments
Open

Enabling wayland for VScode crash the extension #57

jbtrystram opened this issue May 27, 2024 · 0 comments

Comments

@jbtrystram
Copy link

jbtrystram commented May 27, 2024

I run vscode with ELECTRON_OZONE_PLATFORM_HINT=wayland and socket=wayland, getting way less glitch that way.
However this cause devcontainers to fail to open a container :

 Start: Run: podman-remote run --sig-proxy=false -a STDOUT -a STDERR --mount type=bind,src=/run/flatpak/wayland-0,dst=/tmp/vscode-wayland-3a745685-74ae-469c-bd42-b119337164ec.sock -l devcontainer.local_folder=/var/home/jibou/code/github.com/coreos/coreos-assembler -l devcontainer.config_file=/var/home/jibou/code/github.com/coreos/coreos-assembler/.devcontainer.json[....] --entrypoint /bin/sh -l devcontainer.metadata=[{"customizations":{"vscode":{"extensions":["golang.Go","ms-vsliveshare.vsliveshare"]}},"remoteUser":"builder"}] vsc-coreos-assembler-706f51bc2cc16b4cabcbd4acab91208460557c2eff03603c9d48a17c559c58cd-uid -c echo Container started
[2024-05-27T13:52:15.208Z] Error: statfs /run/flatpak/wayland-0: no such file or directory

Disabling wayland allow me to get devcontainers with podman running again. I am not sure if the issue is with this extension or devcontainers though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant