Feature summary (what you would like to be able to do and where):
Currently there are some 'standard' images provided in toolforge:
tools.cluebotng-review@tools-bastion-15:~$ toolforge jobs images +------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------+ | Short name | image | +------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------+ | bookworm | docker-registry.tools.wmflabs.org/toolforge-bookworm-sssd:latest | | bullseye | docker-registry.tools.wmflabs.org/toolforge-bullseye-sssd:latest | | jdk17 | docker-registry.tools.wmflabs.org/toolforge-jdk17-sssd-base:latest | | jdk21 | docker-registry.svc.toolforge.org/toolforge-jdk21-sssd-base:latest | | mariadb | docker-registry.tools.wmflabs.org/toolforge-mariadb-sssd-base:latest | | mono6.12 | docker-registry.tools.wmflabs.org/toolforge-mono612-sssd-base:latest | | mono6.8 | docker-registry.tools.wmflabs.org/toolforge-mono68-sssd-base:latest | | node16 | docker-registry.tools.wmflabs.org/toolforge-node16-sssd-base:latest | | node18 | docker-registry.tools.wmflabs.org/toolforge-node18-sssd-base:latest | | node20 | docker-registry.svc.toolforge.org/toolforge-node20-sssd-base:latest | | perl5.32 | docker-registry.tools.wmflabs.org/toolforge-perl532-sssd-base:latest | | perl5.36 | docker-registry.tools.wmflabs.org/toolforge-perl536-sssd-base:latest | | perl5.40 | docker-registry.svc.toolforge.org/toolforge-perl540-sssd-base:latest | | php7.4 | docker-registry.tools.wmflabs.org/toolforge-php74-sssd-base:latest | | php8.2 | docker-registry.tools.wmflabs.org/toolforge-php82-sssd-base:latest | | php8.4 | docker-registry.svc.toolforge.org/toolforge-php84-sssd-base:latest | | python3.11 | docker-registry.tools.wmflabs.org/toolforge-python311-sssd-base:latest | | python3.13 | docker-registry.svc.toolforge.org/toolforge-python313-sssd-base:latest | | python3.9 | docker-registry.tools.wmflabs.org/toolforge-python39-sssd-base:latest | | ruby2.1 | docker-registry.tools.wmflabs.org/toolforge-ruby21-sssd-base:latest | | ruby2.7 | docker-registry.tools.wmflabs.org/toolforge-ruby27-sssd-base:latest | | ruby3.1 | docker-registry.tools.wmflabs.org/toolforge-ruby31-sssd-base:latest | | ruby3.3 | docker-registry.svc.toolforge.org/toolforge-ruby33-sssd-base:latest | | tcl8.6 | docker-registry.tools.wmflabs.org/toolforge-tcl86-sssd-base:latest | | trixie | docker-registry.svc.toolforge.org/toolforge-trixie-sssd:latest | +------------------------------------------------------------------------+-------------------------------------------------------------------------------------------------+
These all require mounting NFS and are not supported via components.
It would be quite useful to be able to execute these images via components and not have to execute them on NFS workers (which appear to have the worst availability).
Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
- Cron jobs, which execute basic commands such as curl
- Database dumps executed on a schedule (require NFS, but are limited to jobs currently)
Benefits (why should this be implemented?):
- Image reuse - no need for every tool to build their own meta images, saving resources in the registry and on the worker nodes
- Consistency across apis - no need for maintainers to manage both jobs and components
- Reduce NFS usage - no nfs by default