Add mktar_from_directory util

[phlax]

Long story short

I have used aiodocker in a couple of projects, the one thing i find myself implementing is a mktar_from_directory function (or similar) to enable building an image with artefacts

my implementaion/s are very similar to the existing mktar_from_directory, im wondering if it would be helpful to PR this addition

How to reproduce

try to build an image that has artefacts

[asvetlov]

Looks like a great idea.
Would you prepare a pull request? Tests are required, they should be an easy excercise.

[q0w]

@asvetlov does it mean that existing mktar_from_tar just needs a new arg directory and new line with t.add(directory, arcname='.') ?

[asvetlov]

Sorry, I cannot find mktar_from_tar function in the project.

[q0w]

Sorry, mb - mktar_from_dockerfile

[asvetlov]

I think a separate function is needed.
The function should not accept dockerfile argument but a folder (with dockerfile inside usually) to archive.

[phlax]

the most simple implementation would be to send the entire directory/context - ideally it would be able to filter according to any .dockerignore function, but not sure how easy that is in terms of parsing/filtering

[q0w]

Maybe use docker-py implementation with PatternMatcher for .dockerignore?

[phlax]

sounds like a plan, but im guessing we would want to avoid a dependency, so i guess it would be a matter of cribbing it

[q0w]

they also cribbed it from moby

[achimnol]

I'd also suggest refactoring mktar_from_dockerfile and mktar_from_directory to be async context managers that closes the generated file automatically and use asynchronous file I/O (streaming).