kubernetes/minikube

update registry addon documentation

Open

#6,982 opened on Mar 10, 2020

View on GitHub
 (29 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
area/registryco/runtime/criohelp wantedkind/documentationlifecycle/frozenpriority/backlog

Description

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

Contributor guide

Tech stack
godocker
Domain
documentationdevopscloud
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic knowledge of minikubeunderstanding of container runtimesfamiliarity with documentation contributions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.