buildcache docker image is empty
danlipsa opened this issue · comments
@willdunklin Seems that the buildcache docker image is emtpy. The image shows the output from docker dive. Can you help with this? Thanks!
Using BUILDCACHE_VERSION=linux-ubuntu20.04-x86_64-gcc-11.1.0 fixed this issue. I think there is a way to build the docker so that this parameter is passed correctly - I'll figure it out when you are back.
@danlipsa do you know what BUILDCACHE_VERSION version tag you were using before setting it to the version above? It's been a while since I've worked with this process. If you could describe the steps you were taking that led you to the error that would be very helpful!
@willdunklin It was "empty" written in the Dockerfile
https://github.com/SENSEI-insitu/SENSEI/blob/master/.github/ci/docker/ubuntu/Dockerfile
From @willdunklin
The issue you were running into is somewhat expected... The buildcache docker images are only usable iff the architecture you're targeting has a pre-built image on the github container registry. The reason the default is empty is because that will manually build the spack package cache from scratch. There is a script for building/automatically publishing new images to the ghcr in a script within the project: https://github.com/SENSEI-insitu/SENSEI/blob/master/.github/ci/docker/build_image.sh (you will need the proper permissions to upload to the github container registry in order for the script to publish the image it generates)
I hope that helps resolve any lingering confusion about the process there. Essentially the buildcache images aren't necessary at all (hence why having an empty prebuilt buildcache is a valid setting), it would just mean it takes longer to rebuild from scratch