This is really cool!  The first time I tried to run a GUI app in a container, I discovered there&#x27;s a LOT of practical gaps between &quot;okay I have containers&quot; and &quot;I want to run a graphical application&quot;.  Subuser bridges those gaps nicely.<p>My favorite part of reading the docs for subuser is how completely direct and honest they are about security of various features.  E.g., if you enable some features of X bridging, you&#x27;re accepting security risks, because that&#x27;s how X works.  (And if you don&#x27;t need those features, don&#x27;t enable them; it looks like subuser has it down to a one-word config flag, which is <i>amazing</i>.)  By comparison, if you start out on your own... there&#x27;s lots of brief tutorials on the internet about using xephyr, or xpra, or doing something really wildly unsafe like just plain mounting the X sockets in.  But not only are all these things rough to get started on by yourself, the brief explanations thrown around are often not clear on the security implications.  Subuser seems like a great way to do the right things... out of the box.  And with excellent truth in packaging.<p>I&#x27;ve accumulated a lot of scripts in my personal `~&#x2F;bin` over the last couple years that do stuff like &quot;mount cwd and interesting dir $x, make sure image with $prog is here or fetch it, now pass args and invoke $prog with $HOME=...&quot; -- and while these have been really useful to <i>me</i>, they&#x27;ve been ad-hoc and almost impossible to usefully share with others.  Subuser&#x27;s format for making valuable configuration like this <i>sharable</i> is extremely interesting.