مشكلة تسطيب minikube

[ahmedsayedtalib]

الأوامر المطلوبة لإعادة إظهار المشكلة:

النتيجة الكاملة للأمر الذي تعذّر تنفيذه:

😄 minikube v1.33.1 on Almalinux 9.4
✨ Using the docker driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🚜 Pulling base image v0.0.44 ...
🏃 Updating the running docker "minikube" container ...
❗ This container is having trouble accessing https://registry.k8s.io
💡 To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
🐳 Preparing Kubernetes v1.30.0 on Docker 26.1.1 ...
❌ Unable to load cached images: loading cached images: stat /home/ahmedsayed/.minikube/cache/images/amd64/registry.k8s.io/etcd_3.5.12-0: no such file or directory

نتيجة الأمر minikube logs:

إصدار نظام التشغيل المُستخدَم: alma linux 9.4
minikube_update-context_48fe98ec0094acd0c9e724f718cafbbcfe2a39c0_0.log

[medyagh]

@ahmedsayedtalib

"❗ This container is having trouble accessing https://registry.k8s.io/❗ This container is having trouble accessing https://registry.k8s.io/"

are you using a proxy or VPN ? your system seems to not have access rto GCR

[medyagh]

/triage needs-information
/kind support

[spowelljr]

Hi @ahmedsayedtalib, looking at your logs, your kubeconfig is malformed:
decode kubeconfig from "/home/ahmedsayed/.kube/config": decode data: apiVersion: v1.33.1

You have apiVersion: v1.33.1 but it should just be apiVersion: v1.

Open /home/ahmedsayed/.kube/config and change the line to apiVersion: v1 and save your file and I think that will resolve your issue.

---

مرحبًا @ahmedsayedtalib، عند النظر إلى سجلاتك، تجد أن kubeconfig الخاص بك غير صحيح:
decode kubeconfig from "/home/ahmedsayed/.kube/config": decode data: apiVersion: v1.33.1

لديك apiVersion: v1.33.1 ولكن يجب أن يكون apiVersion: v1 فقط.

افتح /home/ahmedsayed/.kube/config وقم بتغيير السطر إلى apiVersion: v1 واحفظ ملفك وأعتقد أن ذلك سيحل مشكلتك.

[kundan2707]

/language ar

[k8s-ci-robot]

@kundan2707: The label(s) language/ar cannot be applied, because the repository doesn't have them.

In response to this:

/language ar

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[spowelljr]

Hi @ahmedsayedtalib, we haven't heard back from you, do you still have this issue?
There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.

---

مرحبًا @ahmedsayedtalib، لم نتلق ردًا منك، هل لا تزال لديك هذه المشكلة؟
لا توجد معلومات كافية في هذه المشكلة لجعلها قابلة للتنفيذ، وقد مرت فترة طويلة بما فيه الكفاية، لذلك من المحتمل أن يكون من الصعب تكرار هذه المشكلة.

سأغلق هذه المشكلة في الوقت الحالي ولكن لا تتردد في إعادة فتحها عندما تشعر أنك مستعد لتقديم المزيد من المعلومات.