On Wed, Aug 21, 2019 at 09:13 Colin Walters wrote:
On Wed, Aug 21, 2019, at 7:34 AM, Daniel Walsh wrote:
> I agree. Entering a container and doing a yum update is an
> Anti-pattern.
This is a complex discussion - I think we need both. Personally I
live inside a "pet" container using
https://github.com/cgwalters/coretoolbox
and I definitely `yum update` inside there, though I do also periodically
destroy it and re-pull.
I also run yum to keep my local runtime updated and I even suggested a
new buildah commit option to make this more efficient:
https://github.com/containers/buildah/issues/1778
Though this is useful for devel or traditional workstation use-case.
It seems like a fedora image should come with the package
manager, but perhaps it should only be used as a build stage using
an option similar to the --installroot option?
Regards,
-Tristan
Kubernetes though for sure is about non-pet containers.
> Buildah and Multi-Stage builds do allow you to eliminate
> these tools, but that is more difficult to do.
multi-stage is easy and obvious for the case of e.g. Golang and Rust single compiled
binaries, and it's not too hard to do for other compiled languages (C/C++) as long as
you have a notion of `BuildRequires` versus `Requires`.
For interpreted languages though, yeah, not as worthwhile unless you're pulling in a
*lot* of build dependencies (doc tooling?) distinct from your runtime ones.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org