search

scheme-containers / monorepo

Generators, website, issues
MIT License
6 stars 1 forks source link

Using debian:stable-slim tag instead of debian:bullseye-slim #19

Open Retropikzel opened 2 weeks ago

Retropikzel commented 2 weeks ago

Would it be possible to use debian:stable-slim tag on the images instead of debian:bullseye-slim? If there is no desire to move to "moving" tag such as debian:stable-slim, then perhaps debian:bookworm-slim could be used?

I'm making a small tool which uses these images as base and installs (and uses) some libraries on top, as bullseye is already old stable the libraries are quite old. Currently I update the Debian to latest stable, but because Debian is swithing to merged usr directory on bookworm the update is quite a hassle (and a hack) and of course it takes a little bit of time on the first run of the container.

So it's this bullseye->bookworm jump that is causing problems. If the tag was already debian:bookworm-slim then updating to for example trixie (Debian testing branch as the time of writing) would also be easy.

lassik commented 2 weeks ago

Thank you for using the containers. Upgrading to bookworm is fine by me.

It's convenient that stable-slim exists, but for reproducibility it's better to specify the Debian version explicitly for each Dockerfile. A few containers use even older versions of Debian since those Scheme implementations are so old. We have alpine versions of some containers, too.

lassik commented 2 weeks ago

If you have an interest in maintaining the containers, I can try to add you to the Docker Hub schemers organization. (scheme was already taken.) We have a free plan; I'm not sure how many users it permits, but I've been inactive.

lassik commented 2 weeks ago

(See also the work-in-progress generator. It's not used to generate the current Dockerfiles, but would really help with the maintenance burden.)

Retropikzel commented 2 weeks ago

Thank you for using the containers. Upgrading to bookworm is fine by me.

It's convenient that stable-slim exists, but for reproducibility it's better to specify the Debian version explicitly for each Dockerfile. A few containers use even older versions of Debian since those Scheme implementations are so old. We have alpine versions of some containers, too.

Thank you for making and maintaining them! They have sped up my testing very much.

I understand, I would do the same at $dayjob too and choose the debian:bookworm-slim so when change happens is controllable.

If you have an interest in maintaining the containers, I can try to add you to the Docker Hub schemers organization. (scheme was already taken.) We have a free plan; I'm not sure how many users it permits, but I've been inactive.

I think we can manage with pull requests too?

What I would like to do is first make a script that builds all the containers, to easily test things. Then I would locally switch to debian:bookworm-slim on all Dockerfiles and see what happens when they are built. Then I'd like to fix everything I can, switch those that can not be fixed back to debian:bullseye-slim and then make a pull request.

I'm just asking before I do anything so I know I will not do it all for nothing. :)

(See also the work-in-progress generator. It's not used to generate the current Dockerfiles, but would really help with the maintenance burden.)

Could you tell me what the generator is supposed to do and what are the pain points in the maintenance?