-
Notifications
You must be signed in to change notification settings - Fork 32
ibm power fixes - add more static cluster minikube fixes #663
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.
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
Conversation
MCK 1.6.2 Release NotesBug Fixes
|
| echo "Removing ~/.minikube/machines/minikube directory..." | ||
| rm -rf ~/.minikube/machines/minikube | ||
| fi | ||
| sudo rm -rf ~/.minikube/machines/minikube 2>/dev/null || true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we use sudo podman (rootful) we also need to ensure minikube gets cleaned up in root space
| sudo podman rm -f registry 2>/dev/null || true | ||
|
|
||
| if ! sudo podman run -d -p 127.0.0.1:5000:5000 --name registry --restart=always docker.io/library/registry:2; then | ||
| if ! sudo podman run -d -p 127.0.0.1:5000:5000 --replace --name registry --restart=always docker.io/library/registry:2; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sometimes cleanup didn't work, so we should just replace the existing/running one
| sudo tee /root/.config/containers/registries.conf << 'EOF' >/dev/null | ||
| [[registry]] | ||
| location = "localhost:5000" | ||
| location = "127.0.0.1:5000" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some loopback misses from prior pr
Summary
This pr fixes some more minikube static container setup steps which i encountered after merging the prior pr.
Proof of Work
Checklist
skip-changeloglabel if not needed