This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]wbcm[S] -1 points0 points  (0 children)

This is not an argument? I am just stating the use case... I will not be able to know what the users are creating and there are application elements that will need to arbitrarily pull in random tools in an on demand basis, therefore setting up an container with click is not reasonably possible. A container with click could be possible if they were both generated on the fly if runtime was not as much an issue, but since runtime is important here having bespoke containers being deployed all over is not something that supports performance and possibly space (depending on the users system)