We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
为了防止被滥用,目前仅仅支持一次同步一个镜像
Issues 必须带 porter label, 简单来说就是通过模板创建就没问题,别抖机灵自己瞎弄。
porter
标题必须为 [PORTER]镜像名:tag 的格式, 例如
[PORTER]镜像名:tag
[PORTER]k8s.gcr.io/federation-controller-manager-arm64:v1.3.1-beta.1
[PORTER]gcr.io/google-containers/federation-controller-manager-arm64:v1.3.1-beta.1
特别的,如果要指定平台的话 [PORTER]镜像名:tag|平台类型
[PORTER]镜像名:tag|平台类型
[PORTER]busybox:latest|linux/arm64
[PORTER]busybox:latest|linux/arm/v7
issues的内容无所谓,可以为空
可以参考 已搬运镜像集锦
注意:
>>>>>>>>本项目目前仅支持 gcr.io、k8s.gcr.io、docker.io、registry.k8s.io、quay.io、ghcr.io 镜像<<<<<<<<
The text was updated successfully, but these errors were encountered:
构建进展
Sorry, something went wrong.
转换完成
#原镜像 registry.k8s.io/sig-storage/csi-snapshotter:v6.3.3 #转换后镜像 anjia0532/google-containers.sig-storage.csi-snapshotter:v6.3.3 #下载并重命名镜像 docker pull anjia0532/google-containers.sig-storage.csi-snapshotter:v6.3.3 docker tag anjia0532/google-containers.sig-storage.csi-snapshotter:v6.3.3 registry.k8s.io/sig-storage/csi-snapshotter:v6.3.3 docker images | grep $(echo registry.k8s.io/sig-storage/csi-snapshotter:v6.3.3 |awk -F':' '{print $1}')
No branches or pull requests
为了防止被滥用,目前仅仅支持一次同步一个镜像
Issues 必须带
porter
label, 简单来说就是通过模板创建就没问题,别抖机灵自己瞎弄。标题必须为
[PORTER]镜像名:tag
的格式, 例如[PORTER]k8s.gcr.io/federation-controller-manager-arm64:v1.3.1-beta.1
[PORTER]gcr.io/google-containers/federation-controller-manager-arm64:v1.3.1-beta.1
特别的,如果要指定平台的话
[PORTER]镜像名:tag|平台类型
[PORTER]busybox:latest|linux/arm64
[PORTER]busybox:latest|linux/arm/v7
issues的内容无所谓,可以为空
可以参考 已搬运镜像集锦
注意:
>>>>>>>>本项目目前仅支持 gcr.io、k8s.gcr.io、docker.io、registry.k8s.io、quay.io、ghcr.io 镜像<<<<<<<<
The text was updated successfully, but these errors were encountered: