Re: [atomic-devel] Live container updates without in-container DNF

[Nick Coghlan <ncoghlan gmail com>]

On 15 October 2015 at 17:56, Pavel Odvody <podvody redhat com> wrote:
> Hello,
>
> at [0] is a rationale and description of the process, whereas at [1] is
> the final code.
> The example uses hosts DNF but could be easily extrapolated and use DNF
> via another (spc) container (Atomic use-case).
>
> [0]: https://docs.google.com/document/d/1dsStqcuZTeeu3BgwZwmX2zRsuYJoD9Qt9I3SQA9F7Lc/pub
> [1]: https://github.com/shaded-enmity/dnf-container-update

Could this be adapted to do container builds in a way where the build
container is separate from the container being built? (At the moment,
s2i still has the two merged, so you end up with build tools and
artifacts in your runtime container by default)

Regards,
Nick.

-- 
Nick Coghlan   |   ncoghlan gmail com   |   Brisbane, Australia