Yuvi

This sounds good to me, @craig-willis! re 'fetch only mode', you can do that with the library right now - and I think you should be able to just use...

Yeah, scalability improved massively for kubespawner with this change. +1 for making it happen for docker too!

@davidjsherman not sure of the specifics, but perhaps look at the paths that are being chowned, and see what tests already cover them? Then, a gid variant can be added...

@tmhm as far as I know, none! Probably a good issue for someone new to pick up and build. Maybe you! :)

It could be something like 'verify' that runs like postBuild, and should exit cleanly for success or non-cleanly for failure. I don't know how useful it will be, however, or...

I do like the idea. However if it runs an expensive test suite that might take quite a while. Would we want to limit the amount of time this could...

Thanks for working on this, @craig-willis! Exciting progress. My preliminary thoughts are: 1. repo2docker itself should verify that it is compatible with the version specified, and if not, quit with...

> What I had in mind was that (for the moment?) add a new script called (say) `repo2docker-pinned` that fetches the repo, figures out the version, concocts a command like...

Replacing asynchronize with this sounds like a great idea!

I've opened https://github.com/jupyter/repo2docker/issues/682 to talk very specifically about cases where docker daemon isn't useful.