Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add pluggable image name substitution

未关闭
#1,570 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, typescript

调研方向

Start with packages/testcontainers/src/container-runtime/image-name.ts and trace how ImageName is built for Ryuk and SSHD. The issue leaves the scope of Compose images and Dockerfile FROM lines undecided, and depends on configuration work in #1569. Done means image pulls pass through the configured substitutor, with the existing prefix variable as the default.

由索引模型根据 Issue 内容生成。

描述

enhancement minor

What happens

The only way to redirect image pulls is TESTCONTAINERS_HUB_IMAGE_NAME_PREFIX, which prefixes Docker Hub image names. It cannot:

  • map other registries (ghcr.io, quay.io, mcr.microsoft.com) to a mirror
  • apply different rules to different images
  • rewrite a tag or a digest

Organisations that mirror everything through an internal registry end up editing image names in every test.

Expected

A function that every image name passes through before it is pulled, registered in configuration:

TestContainers.configure({
  imageNameSubstitutor: (image) => (image.registry === "ghcr.io" ? image.withRegistry("mirror.example.com/ghcr") : image),
});

The existing prefix variable becomes the default substitutor.

Where

  • packages/testcontainers/src/container-runtime/image-name.ts
  • the places that build ImageName for Ryuk and SSHD

Notes

  • Java has a pluggable ImageNameSubstitutor, with PrefixingImageNameSubstitutor as the built-in equivalent of the prefix variable. Go has WithImageSubstitutors.
  • Decide whether images named in Compose files and Dockerfile FROM lines are in scope.

Dependencies

  • Blocked by #1569: the substitutor is registered through configuration.
主要语言
TypeScript
星标
2.6k
派生
274
平均合并
1 天 14 小时
30 天内合并 PR
44

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

testcontainers/testcontainers-node 的其他 Issue

查看 testcontainers/testcontainers-node 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。