kubernetes/minikube

update registry addon documentation

Open

#6,982 建立於 2020年3月10日

在 GitHub 查看
 (29 留言) (0 反應) (0 負責人)Go (31,799 star) (5,222 fork)batch import
area/registryco/runtime/criohelp wantedkind/documentationlifecycle/frozenpriority/backlog

描述

The exact command to reproduce the issue:

minikube start --addons=registry --container-runtime=cri-o

The full output of the command that failed:

Pods fail to pull image from the registry, e.g.:

image: localhost:5000/mycontainer

Note that I can push to the registry from outside via docker://$(minikube ip):5000/mycontainer.

Switching to Docker runtime allows this to work.

The operating system version:

Fedora 31

貢獻者指南

技術棧
godocker
領域
documentationdevopscloud
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
basic knowledge of minikubeunderstanding of container runtimesfamiliarity with documentation contributions
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Examine the existing registry addon documentation in the minikube repository, likely in the docs/ directory. Review the comments in issue #6982 to understand the required clarifications, particularly regarding compatibility with the cri o runtime. Consult the maintainer's comments to identify the exact documentation changes needed, such as updating prerequisites or notes about runtime support.