Skip to content

403 bad reponse #20337

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

Open
SARIBEG10 opened this issue Jan 29, 2025 · 4 comments
Open

403 bad reponse #20337

SARIBEG10 opened this issue Jan 29, 2025 · 4 comments
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@SARIBEG10
Copy link

What Happened?

i got below error when try to run minikube by this command

minikube start --driver=docker --base-image=ghcr.io/kubernetes/minikube/kicbase:v0.0.17 --kubernetes-version=v1.23.3

Attach the log file

X Exiting due to K8S_INSTALL_FAILED: Failed to update cluster: update primary control-plane node: downloading binaries: downloading kubectl: download failed: https://dl.k8s.io/release/v1.23.3/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.23.3/bin/linux/amd64/kubectl.sha256: getter: &{Ctx:context.Background Src:https://dl.k8s.io/release/v1.23.3/bin/linux/amd64/kubectl?checksum=file:https://dl.k8s.io/release/v1.23.3/bin/linux/amd64/kubectl.sha256 Dst:/home/test/.minikube/cache/linux/amd64/v1.23.3/kubectl.download Pwd: Mode:2 Umask:---------- Detectors:[0x59db520 0x59db520 0x59db520 0x59db520 0x59db520 0x59db520 0x59db520] Decompressors:map[bz2:0xc00012d168 gz:0xc00012d1f0 tar:0xc00012d1a0 tar.bz2:0xc00012d1b0 tar.gz:0xc00012d1c0 tar.xz:0xc00012d1d0 tar.zst:0xc00012d1e0 tbz2:0xc00012d1b0 tgz:0xc00012d1c0 txz:0xc00012d1d0 tzst:0xc00012d1e0 xz:0xc00012d1f8 zip:0xc00012d200 zst:0xc00012d210] Getters:map[file:0xc001b70320 http:0xc0004e31d0 https:0xc0004e3220] Dir:false ProgressListener:0x59a54e0 Insecure:false DisableSymlinks:false Options:[0x17e6480]}: invalid checksum: Error downloading checksum file: bad response code: 403

Operating System

Ubuntu

Driver

Docker

@medyagh
Copy link
Member

medyagh commented Jan 29, 2025

@SARIBEG10 I am curious what version of minikube do you use, and I am more curious why do you pass a very old Kicbase image ? it seems like kubernetes u are trying to use is so old that those binaries dont exist on the kubernetes website anymore.
but I think u could download an older minikube and it should be preloaded into the ISO/Base image

Please attach (drag) thelogs.txt file to this issue which can be generated by running this command:

$ minikube logs --file=logs.txt

This will help us isolate the problem further. Thank you!

/triage needs-information
/kind support

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Jan 29, 2025
@medyagh
Copy link
Member

medyagh commented Jan 29, 2025

@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2025
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy