James Netherton
James Netherton
I can reproduce the problem at least. Let me see if can fix it and push an updated image.
A possible (not ideal) workaround for now would be to run the container in privileged mode. E.g with the `--privileged` argument.
In your example, you have some extra space between `--` and `privileged`. Try removing it. E.g it should be `--privileged`.
For me it's working in privileged mode.... One thing to check, is the permissions on your host machine for the `.atom` directory with `ls -ld ${HOME}/.atom`. The owner should be...
Ok - then I guess it's not an issue with permissions. I don't use Windows or Docker Desktop so it's hard for me to figure out what's wrong for you....
That command is meant for running on the host machine, not the container. I guess for Docker Desktop on Windows the Docker host is actually a Linux VM. Presumably it...
I'll have to experiment to see if I can reproduce it. It's not something that I have come across in the past. But, I've moved to VS Code so I...
I'm running Fedora 25 with i3. I get the `Failed to launch GPU process` message, but there's no freezing. Adding the `libgl1-mesa-glx libgl1-mesa-dri` packages fixes up the error. I'll try...
I can't replicate your hardware but I tested in a Kubuntu 17.04 VM. I still see the errors you mentioned earlier in the console output, but there is no freezing....
Yes, could be related to `kwin`. Maybe try to obtain some [debug logs](https://community.kde.org/KWin/Debugging)?