CT team: I was talking to some enterprise container builders at LinuxCon, and one thing which came up as a tooling request was some way to encourage/enforce making developers re-use shared container layers, and track if they had.
The basic idea is that it's a "best practice" to make reusable layered containers with foundational technology and re-use them -- among other things, to simplify security updates. So for example, this would be good inherited container heirarchy for a GeoDjango container: Fedora24 | Python27 | Django | GeoDjango | MyGeoDjangoApplication And this would be a poor one: Fedora24 | MyGeoDjangoApplication But AFAIK, there aren't any tools to encourage or check for the first over the second. -- -- Josh Berkus Project Atomic Red Hat OSAS _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
