ENHANCEMENT: Option run container interactive

[peter1000]

eventhough subuser is about running apps - sometimes I find myself in the need to inspect a container: e.g. to test some apt-get install updates ect..

till now one has to go through docker: e.g.

sudo docker run -i -t subuser-firefox_libx11_libubuntu_trusty /bin/bash

I suggest adding something similar to subuser run: e.g to a new logo to subuser program:
firefox_libx11_libubuntu_trusty container

$ subuser run firefox_libx11_libubuntu_trusty --container

keep common task in subuser interface

[peter1000]

in the seldom case that a progrm docker image has n /bin/bash one will get an error:
one option would be to specify such in the permissions.json

e.g.
allow-interactive:

or
path-to-shell: I prefer this because it solves 2 problem:

• define if there is an shell
• and also the path to the shell:

then one can do something to:

 try:
     pathToShelll = permissions["path-to-shell"]
     dockerCommand = "docker run -i -t bla bla  pathToShelll"

[peter1000]

BTW: I did not know one can pass on on arguments to the program through subuser run it should be mention in the help.

[peter1000]

I'm working now on this and will send later a proposed pullrequest

[timthelion]

I don't like this idea. I don't see a reason to duplicate functionality that docker already manages just fine.
Sorry :(

[peter1000]

can be close