<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thank Jason and Mark,<div class=""><br class=""></div><div class="">I think just adding another tag at the end of the build process is what we are going to do.</div><div class=""><br class=""></div><div class="">On a related note doe anyone have any tips on how to version a horizon container because it has multiple repos inside.</div><div class=""><br class=""></div><div class="">Eg. We have the source for horizon and then source for each plugin which have different versions.</div><div class="">With Debian they are all separate debs and installed differently with separate version and makes tracking things really easy.</div><div class=""><br class=""></div><div class="">In the container world it makes it a bit harder.</div><div class="">I’m thinking we need to have our kolla-build.conf specify specific git refs and then when we update this file incorporate that somehow into the versioning.</div><div class=""><br class=""></div><div class="">Sam</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Oct 2021, at 2:47 am, Jason Anderson <<a href="mailto:jasonanderson@uchicago.edu" class="">jasonanderson@uchicago.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Sam, I think Mark’s idea is in general stronger than what I will describe, if all you’re after is different aliases. It sounds like you are trying to iterate on two images (Barbican and Nova), presumably changing the source of the former frequently, and don’t
want to build the entire ancestor chain each time.
<div class=""><br class="">
</div>
<div class="">I had to do something similar because we have a fork of Horizon we work on a lot. Here is my hacky solution: <a href="https://github.com/ChameleonCloud/kolla/commit/79611111c03cc86be91a86a9ccd296abc7aa3a3e" class="">https://github.com/ChameleonCloud/kolla/commit/79611111c03cc86be91a86a9ccd296abc7aa3a3e</a></div>
<div class=""><br class="">
</div>
<div class="">We are on Train w/ some other Kolla forks so I can’t guarantee that will apply cleanly, but it’s a small change. It involves adding build-args to some Dockerfiles, in your case I suppose barbican-base, but also nova-base. It’s a bit clunky but
gets the job done for us.</div>
<div class=""><br class="">
</div>
<div class="">/Jason</div>
<div class="">
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On Oct 7, 2021, at 3:41 AM, Mark Goddard <<a href="mailto:mark@stackhpc.com" class="">mark@stackhpc.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Sam,<br class="">
<br class="">
I don't generally do that, and Kolla isn't really set up to make it<br class="">
easy. You could tag the base containers with the new tag:<br class="">
<br class="">
docker pull <prefix>-base:wallaby<br class="">
docker tag <prefix>-base:wallaby <prefix>-base:<git describe output><br class="">
<br class="">
Mark<br class="">
<br class="">
On Thu, 7 Oct 2021 at 03:34, Sam Morrison <<a href="mailto:sorrison@gmail.com" class="">sorrison@gmail.com</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
I’m trying to be able to build a projects container without having to rebuild the parents which have different tags.<br class="">
<br class="">
The workflow I’m trying to achieve is:<br class="">
<br class="">
Build base and openstack-base with a tag of wallaby<br class="">
<br class="">
Build a container image for barbican with a tag of the version of barbican that is returned when doing `git describe`<br class="">
Build a container image for nova with a tag of the version of barbican that is returned when doing `git describe`<br class="">
etc.etc.<br class="">
<br class="">
I don’t seem to be able to do this without having to also build a new base and openstack-base with the same tag which is slow and also means a lot of disk space.<br class="">
<br class="">
Just wondering how other people do this sort of stuff?<br class="">
Any ideas?<br class="">
<br class="">
Thanks,<br class="">
Sam<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div></blockquote></div><br class=""></div></body></html>