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
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
The text was updated successfully, but these errors were encountered:
I run vscode with
ELECTRON_OZONE_PLATFORM_HINT=wayland
andsocket=wayland
, getting way less glitch that way.However this cause devcontainers to fail to open a container :
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
The text was updated successfully, but these errors were encountered: