<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 17, 2017 at 9:52 AM, Lance Ball <span dir="ltr"><<a href="mailto:lball@redhat.com" target="_blank">lball@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks for the reply Ben. Adding everyone else back in...<div><br></div><div>I honestly don't mean to be obtuse here, but I'm still a little confused. Please bear with me and a couple more questions.<br><div><br><div class="gmail_quote"><span class=""><div dir="ltr">On Thu, Mar 16, 2017 at 7:40 PM Ben Breard <<a href="mailto:bbreard@redhat.com" target="_blank">bbreard@redhat.com</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg">I mean that fedora and centos will have versions of the rhel7-atomic image. With this we can potentially create smaller s2i and other useful things. ...but I have no other insight on who maintains what. sorry </div></div></div></div></blockquote><div><br></div></span><div>I don't understand how Fedora and CentOS can have "versions of the "rhel7-atomic" image. Do you mean that there will be "atomic" (and therefore hopefully, smaller) images for these OSs? So, we'd have something like fedora-atomic and centos-atomic?</div></div></div></div></div></blockquote><div><br></div><div>rhel7-atomic is a base image built from Red Hat Enterprise Linux rpms. The fedora & CentOS versions will be very similar, but composed from fedora & centOS rpms. I have encouraged them to adopt the same naming scheme, but that wasn't something that fedora was super excited about. I don't know where that landed, and someone from Fedora would need to comment on where that's at.</div><div><br></div><div>Looping in Dusty & KB to get more info on this. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><blockquote class="gmail_quote m_6411223969741120767gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><span class="m_6411223969741120767m_-8407162275565778439gmail- m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg">I'm confused why you would need to install httpd, etc in a base builder image. Shouldn't a base s2i builder image just be the minimal requirements to support runtime execution in the OpenShift environment?<br></div></span></div></div></blockquote></div></div></div><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg">yes!!! Here's the list:</div><div class="m_6411223969741120767gmail_msg"><br class="m_6411223969741120767gmail_msg"></div><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> INSTALL_PKGS="autoconf \</div><div class="m_6411223969741120767gmail_msg"> automake \</div><div class="m_6411223969741120767gmail_msg"> bsdtar \</div><div class="m_6411223969741120767gmail_msg"> bzip2 \</div><div class="m_6411223969741120767gmail_msg"> findutils \</div><div class="m_6411223969741120767gmail_msg"> gcc-c++ \</div><div class="m_6411223969741120767gmail_msg"> gd-devel \</div><div class="m_6411223969741120767gmail_msg"> gdb \</div></div></div></div></div></blockquote><div><br></div></span><div>Why would a plain vanilla builder image need gdb, gcc, gcc-c++, gd-devel and make (below)? I suppose for projects that require compilation during the build step this makes sense. But isn't that specific to a runtime platform/language? E.g. if I'm running a Ruby application, why on earth would I want my runtime image to contain gd-devel and gdb? And to be honest, even for compiled projects, gdb seems a bit overkill for a runtime build environment.</div></div></div></div></div></blockquote><div><br></div><div>Great question for the s2i team. I suspect it's because these packages are needed for a small number of rhscl containers, so they get added to the "base". Again, hopefully someone else on this thread knows more about s2i than myself.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div class="gmail_quote"><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> gettext \</div><div class="m_6411223969741120767gmail_msg"> git \</div><div class="m_6411223969741120767gmail_msg"> libcurl-devel \</div><div class="m_6411223969741120767gmail_msg"> libxml2-devel \</div><div class="m_6411223969741120767gmail_msg"> libxslt-devel \</div><div class="m_6411223969741120767gmail_msg"> lsof \</div><div class="m_6411223969741120767gmail_msg"> make \</div></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> mariadb-devel \</div><div class="m_6411223969741120767gmail_msg"> mariadb-libs \</div></div></div></div></div></blockquote><div><br></div></span><div>Why include MariaDB by default in the builder images? Most projects won't use this will they? Or is it specific to OpenShift's needs?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> openssl-devel \</div><div class="m_6411223969741120767gmail_msg"> patch \</div><div class="m_6411223969741120767gmail_msg"> postgresql-devel \</div></div></div></div></div></blockquote><div><br></div><div>Same question as above. Why include this unless it's needed by OpenShift itself.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> procps-ng \</div><div class="m_6411223969741120767gmail_msg"> scl-utils \</div><div class="m_6411223969741120767gmail_msg"> sqlite-devel \</div></div></div></div></div></blockquote><div><br></div><div>Ditto...</div><span class=""><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="m_6411223969741120767gmail_msg"><div class="gmail_extra m_6411223969741120767gmail_msg"><div class="gmail_quote m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"><div class="m_6411223969741120767gmail_msg"> tar \</div><div class="m_6411223969741120767gmail_msg"> unzip \</div><div class="m_6411223969741120767gmail_msg"> wget \</div><div class="m_6411223969741120767gmail_msg"> which \</div><div class="m_6411223969741120767gmail_msg"> yum-utils \</div><div class="m_6411223969741120767gmail_msg"> zlib-devel" && \</div></div></div></div></div></blockquote><div><br></div></span><div>Devel libs seem unnecessary?</div><div><br></div><div>I guess on the whole, I think the base builder images for any given operating system should have only enough in them to fulfill OpenShift requirements. After that, it seems that subsequent builder images that layer on top of these should be responsible for handling their own dependencies. So, it's confusing to me why we would need to include all of this extraneous stuff in the builder images.</div><div><br></div></div></div></div></div></blockquote><div>I would definitely be supportive of this, but I would leave the decision to the responsible teams.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div class="gmail_quote"><div></div><div> Thanks</div><span class="HOEnZb"><font color="#888888"><div>Lance </div></font></span></div></div></div></div> </blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><br><font size="1">Ben Breard</font></div><div><font size="1">Sr Technology Product Manager - Linux Containers</font></div><div dir="ltr"><font size="1">Mobile: 972-816-9081</font><br></div></div></div></div></div></div></div></div></div></div> </div></div>