Timothy Hobbs

Another way of implementing multi-arch support, which I had considered, and which would be easier for users and harder for maintainers, is that [`subuser-version-constraints`](http://subuser.org/subuser-standard/repositories.html#the-subuser-json-file) could be used. That would mean...

This is a good idea. I think, going off the example of git, we could call it `subuser bundle`...

I will work on going over all your comments tomorrow. It's 1 am here, and I want to think this through properly...

It just occured to me, that putting the image-id into the filename won't work on Windows due to the 255 character long path restriction.

I think that we shouldn't worry about that though. Some advanced features may not be supported on outdated operating systems ;)

That would be fine. But don't put the program name in the name of the files. It is simpler to progam if the names are standard.

I beleive that moving away from Docker (which really seems to need to happen due to performance and cleanliness problems) will resolve this issue.

Docker in general doesn't support this afaik. Or does it? You can always use unix's yes command: https://en.wikipedia.org/wiki/Yes_(Unix) On 05/26/2017 08:15 PM, Matteo Signer wrote: > > stdin is not...

Are you running as root or as a normal user? What is the value in $HOME?

Well it is running sudo under the hood: https://github.com/subuser-security/subuser/blob/master/logic/subuser#L51 If you don't want it to run sudo, you can add yourself to the docker group. Then it won't run sudo....