No Documentation

[moredhel]

I'm currently working on trying to transition some containers to using Smith. I am interested in the project and am looking for documentation which would help with not having to read through the source (my current solution).

Is there a source of documentation that I can refer to? If so, it may be worth linking to it in the README.

[vishvananda]

Hi. Unfortunately we don't have any additional official documentation. There is an example of container building in my article which my provide some useful help:

https://hackernoon.com/how-to-build-a-tiny-httpd-container-ae622c37db39

[moredhel]

Thanks Vish, I have already read through it a few times, and yes, the documentation does clarify a few things that aren't clear in the README.md. I found your tempate: https://github.com/vishvananda/smith-inception/blob/master/smith.template.yaml which is a nice overview of some of the commands.

Is it possible to run commands and construct images rather than work in a reductive form? Initially this comes across as a potential replacement for Dockerfiles, but on a second pass it feels more like a second pass optimization on the current system (Which may be somewhat encapsulated by the new Docker multi-stage build files).

Note that I am not evaluating this tool in the context of support of RPM.

Thanks

[vishvananda]

Yes you are right. Without rpms it is more like a second pass optimization. If people like the idea I could see most the functionality being added to the docker copy command for multistage builds. For example COPY --from=0 --deps --strip-ownership /usr/bin/cat /usr/bin/cat Or something Vish

…

On Fri, Aug 11, 2017, 7:06 AM Hamish ***@***.***> wrote: Thanks Vish, I have already read through it a few times, and yes, the documentation does clarify a few things that aren't clear in the README.md. I found your tempate: https://github.com/vishvananda/smith-inception/blob/master/smith.template.yaml which is a nice overview of some of the commands. Is it possible to run commands and construct images rather than work in a reductive form? Initially this comes across as a potential replacement for Dockerfiles, but on a second pass it feels more like a second pass optimization on the current system (Which may be somewhat encapsulated by the new Docker multi-stage build files). Note that I am *not* evaluating this tool in the context of support of RPM. Thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIrjmQvsypcBer-x8eWb1n10TwzKvsDks5sXF_4gaJpZM4OzOrq> .

[moredhel]

Thank you for the helpful comments and clarifications on where Smith is placed in the Image build pipeline.