On 03/22/2017 12:46 AM, Karanbir Singh wrote: > I would prefer to get the build script to produce that, and run it in > sync with the other builds at the same time. Yes, that would be ideal. In fact, we built the image using the same script, we just need to alter some pieces of software around it (see my answer below). Since we need to wait until we get the missing patches in the distro anyway, maybe we could work something out like building on our side or running the script I made? > whats missing for the process to work the same as the x86_64 image ? We are missing patches in lorax, virt-manager and sig-cloud-instance-build, respectively: https://github.com/rhinstaller/lorax/pull/149 https://github.com/virt-manager/virt-manager/commit/cd35470e3c55aa64976cd0a96a6cfd756f71de17 https://github.com/CentOS/sig-cloud-instance-build/pull/65 Regarding publishing the image to docker registry, I don't think the same process used for x86_64 would work because ppc images should go to centos/ppc64le. Like Murilo said in the previous email, we couldn't find how aarch64 images are pushed to centos/aarch64, there are still some black boxes we need to understand so that we could do the same for pcc64le. > i dont see why docker build would need any sort of virtualisation at all ? It doesn't need virtualization, but that's what is being currently used for x86_64, is it not? See: https://github.com/CentOS/sig-cloud-instance-build/blob/master/docker/containerbuild.sh#L69 >> We have not had a chance to look at Container Pipeline yet, we hope to >> look at it soon. > > container pipeline will build above the base, for layered images - not > the base itself. This was meant as future steps, after we have the base image.