[Design Discussion] Do we still need to rely on the container-images repository? #763
Description
Do we still need container-images?
This repository currently provides base container images used by DiracX. Over time, a number of issues have accumulated around:
- base image maintenance and updates (Rebuild diracx*:dev images when we have a new image here container-images#13)
- overlap with what is already defined in DiracX (https://github.com/DIRACGrid/container-images/blob/main/base/environment.yml)
A suggestion was recently raised that this repository might no longer be necessary, and that we could instead run pixi directly in the diracx Dockerfile(s), removing the need for separate base images.
Before acting on this, it seems useful to step back and have an explicit design discussion.
Once this discussion converges, we can:
- either reaffirm the role of this repository and clean it up accordingly
- or plan deprecation and close/block related issues here
I temporarily block existing issues in this repository until we have a clearer architectural direction.