Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

NO-ISSUE: fix for subsystem HTTP registry #5964

Merged
merged 1 commit into from
Feb 8, 2024
Merged

NO-ISSUE: fix for subsystem HTTP registry #5964

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/dev/running-test.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,14 +33,14 @@ First we must prepare the minikube cluster -
podman network rm minikube || true

# Start minikube
minikube start --driver=podman --addons dashboard --force
minikube start --insecure-registry=$(hostname --ip):5000 --driver=podman --addons dashboard --force

# enable the registry addon using quay.io images (to overcome docker-hub's rate-limiter)
minikube addons enable registry --images="Registry=quay.io/libpod/registry:2.8"

# Make the registry addon accessible locally:
nohup kubectl port-forward svc/registry 5000:80 -n kube-system &>/dev/null &
export LOCAL_SUBSYSTEM_REGISTRY=localhost:5000
nohup kubectl port-forward svc/registry --address 0.0.0.0 5000:80 -n kube-system &>/dev/null &
export LOCAL_SUBSYSTEM_REGISTRY=$(hostname --ip):5000

echo "Waiting for registry to become ready..."
while ! curl --location $LOCAL_SUBSYSTEM_REGISTRY; do
Expand Down