x11docker: Could not run kodi container on pure wayland machine via x11docker
Trying to run kodi via
x11docker -- wayland -- tty --gpu --alsa --homedir /home/docker erichough/kodi
gets
invalid volume specification: '/run/user/1000/:/:rw' invalid mount config for type "bind": destination can't be '/'.
Adding "-v /run/user/1000:/tmp:rw" doesn’t help.
XDG_RUNTIME_DIR is manually set and exported on a host machine.
I’m not quite familiar with docker yet so I probably would need some directions…
UPDATE: XDG_RUNTIME_DIR being unset makes the "/:/:rw" instead
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (9 by maintainers)
Commits related to this issue
- --wayland: catch invalid option combinations like --tty #166 — committed to mviereck/x11docker by mviereck 5 years ago
- shebang 'bash -i +H' to make script interactive. #166 #176 — committed to mviereck/x11docker by mviereck 5 years ago
- --weston: use weston-launch if possible/tty interactive #166 — committed to mviereck/x11docker by mviereck 5 years ago
- --enforce-i: experimental option to enforce bash interactive mode #166 #176 — committed to mviereck/x11docker by mviereck 5 years ago
Well, I believe it’s how the unix shell works: creating separated instance on sub-command. If it’s the root of the issue, it’s unresolvable. So only
westoncommand is probably applicable, notweston-launch. Meanwhile usingXwaylandvs. Xorg is completely pointless – just creating extra entity, that’s it. JFYI: I could not create pure wayland-based environment on my test notebook yet: X11 is pulled in anyway by other package’s dependencies. However, having putxwayland disableintosway’s config I made X not to run at all. All the apps are working under wayland environment. So yes, creating purewaylandmachine is theoretically possible. However it would demand massiveebuildreworking to fine-tune the deps. BTW I used Funtoo for this. Wanted to try it out for some time. Thanks for your efforts!