On Fri, Apr 29, 2016 at 7:55 AM, Colin Walters <walters@xxxxxxxxxx> wrote: > On Thu, Apr 28, 2016, at 06:52 PM, Adam Miller wrote: > >> Docker Layered Image "packaging" Guidelines [1] > > This current design means Dockerfiles are always secondary shims. > I think the most interesting case is for new services which are > Docker/container only at least upstream. > Yes, for now that is the case. In the future we want to enable Docker-only content, but the current thought is to start small before opening the floodgates and then work to make sure we have some level of validation along the pipeline. We have validation in place for RPMs and we will eventually for Docker Images, just not there yet. > Do we e.g. require systemd unit files for the RPM that contains the code? > I don't think we should, but the current page says "packaged properly as RPMs" > which implies all current RPM requirements. Yes, the initial goal here is to just wrap pre-existing sets of RPMs into Docker Images to provide out-of-the-box runnable services. From there we can decide what all we want to do with these and what capabilities will be required to enable a more flexible workflow in the future. > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
