Timothy Hobbs

File access is difficult, it is impossible to "Just open a file" from within a subuser

2

This is of course by design, but it would be better to give the user the ability to send a file to a subuser, or somehow consent to the subuser...

Subuser's build and update system should be a separate tool

1

Subuser currently has a dependency resolver and build system. This is currently integrated with the subuser standard. The system is good, but the integration with subuser is not sufficiently unix...

There is no way to mark a base image as needing to be updated and update it.

2

So if the "debian" base image is out of date, subuser never updates that image and never updates "everything" as it should.

This needs a fix on the Docker side. I don't see how Docker can make building images more efficient/quick, but they should move towards block level [CAS](https://en.wikipedia.org/wiki/Content-addressable_storage) for both image...

Don't try to rebuild them over and over again. Try rebuilding only at the user's request.

uname -a leaks information about the host

1

``` timothy@ae3ade92f658f37635fb:/subuser-gui$ uname -a Linux ae3ade92f658f37635fb 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux ```