
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可:
请先完整阅读并严格遵守以下文档中的全部规则与要求:
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
Playground for demonstrating KubeVirt in OLM
docker build -t docker.io/djzager/kubevirt-operators:$(git rev-parse --short HEAD) -f Dockerfile . and docker push docker.io/djzager/kubevirt-operators:$(git rev-parse --short HEAD)) OR choose from
https://hub.docker.com/r/lveyde/kubevirt-operators/tags or
https://hub.docker.com/r/djzager/kubevirt-operators/tags that have
already been built.kubevirt-operator.catalogsource.yaml with your container image
of choice. Want to know more about the base container image? https://github.com/operator-framework/operator-registry/kubectl create -f kubevirt-operator.catalogsource.yaml at this point you
should be able to see the kubevirt and cdi operators in the UI under
Operator Management. You should also see a pod started for a
kubevirt-operators image started up in the
openshift-operator-lifecycle-manager namespace.grpc type catalogsource. This has the caveat that we'll need to "Subscribe"
to our operator in the kubevirt namespace to align with the ServiceAccount
that we reference
here and
here. With
the added benefit of allowing us to aggregate roles, like
here.kubevirt namespace
we must first kubectl create namespace kubevirt and kubectl create -f kubevirt-operator.operatorgroup.yaml.kubevirt
throught the UI or by creating a subscription object. (Maybe want to add a
subscription to this project for reference)kubevirt-operators image is
based on https://github.com/operator-framework/operator-registry/您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
来自真实用户的反馈,见证轩辕镜像的优质服务