Florian Goth (0d6fe119) at 05 Sep 15:25
add remaining base images
Florian Goth (1235de82) at 03 May 18:44
first bookworm images
Florian Goth (6dbd2f33) at 03 May 15:50
gfortran template
Florian Goth (15b382b5) at 02 May 19:30
first bookworm Dockerfile
Florian Goth (c487bed9) at 02 May 15:58
try bookworm
Florian Goth (a0bdaadf) at 02 May 14:38
more bugfixes
Florian Goth (5292481f) at 02 May 14:35
more bugfixes
Florian Goth (7bba9836) at 02 May 14:26
bugfix
Florian Goth (52d7680c) at 02 May 14:19
add freexian GPG key to baseimage
Florian Goth (5474fb00) at 02 May 14:04
add freexian GPG key to baseimage
Florian Goth (d18312d4) at 02 May 13:54
add freexian GPG key to baseimage
Florian Goth (3568073a) at 02 May 13:36
try the freexian eLTS servers
Florian Goth (a2796653) at 02 May 13:32
try the freexian eLTS servers
I added curl and zlib-dev in the CI after HDF5 didn't succeed. My guess is that cmake does not pull the curl binary and the zlib developent files.
Considering generic vs specific containers: I like the idea of having containers that explicitly say in their name that they fill the requirements for ALF/pyALF.
perfect! If you chain the two run commands(if possible) no additional docker layer will be generated and hence the image should be smaller.
curl and zlib are probably generically useful, but I think any image that includes cmake at least pulls in the respective libraries libcurl and libz. So you can use one of those.
When starting from those generic packages, there are usually some small things missing, e.g. Curl and the Zlib libraries, so the package manager has to be executed for that, which kinda feels like it defeats the purpose of the prebuilt images.
I guess putting those specific images in the general registry doesn't make much sense, now that you say it, so we could create an ALF specific registry. I just want to get rid of dealing with package managers in the CI, since I find it annoying.
Script 1 almost seems redundant, why don't you start from one like https://git.physik.uni-wuerzburg.de/Z03/pdi/-/blob/master/debian/bullseye-gfortran-blas-lapack-fftw-hdf5-scipy3/Dockerfile or the others and you basically have everything you need?
Script 2 uses pip for standard debian packages. Try to avoid pip. If you need to use a specific version of a package that you cannot get from apt, at least specify the version you require. If you always require the latest development version of a package, then the pip call is better handled by the CI and your package versions in the image do not depend on the regeneration schedule of the images.
More generally, if the images are ALF specific, they are probably more suited to ALF's registry, and I don't see why I should put them under the "generic images" umbrella. Although I admit, we can discuss changes to the existing images, or maybe we see something that looks generically usable.
I suggest adding images that satisfy the ALF and pyALF requirements, like these two bullseye images. This saves the juggling of installing packages in the GitLab CI configurations.
What do you think, @fgoth?
Florian Goth (c2786147) at 12 Jan 13:19
Have sphinx + plantuml support available in the basic image