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.

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

kube-proxy windows images is not correct (v1.29.8) #379

Open
thdrnsdk opened this issue Oct 17, 2024 · 1 comment
Open

kube-proxy windows images is not correct (v1.29.8) #379

thdrnsdk opened this issue Oct 17, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@thdrnsdk
Copy link

thdrnsdk commented Oct 17, 2024

Describe the bug
A clear and concise description of what the bug is.
kube-proxy windows images is not correct (v1.29.8)

https://hub.docker.com/r/sigwindowstools/kube-proxy/tags?name=v1.29.8

the image size is 26.34 KB

and it's result was

Program 'kube-proxy.exe' failed to run: The file or directory is corrupted and unreadableAt line:1 char:1
+ .\kube-proxy.exe --version
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ .\kube-proxy.exe --version
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

that means this official image wrong

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Kubernetes (please complete the following information):

  • Windows Server version:
  • Kubernetes Version:
  • CNI:

Additional context
Add any other context about the problem here.

Tasks

Preview Give feedback
No tasks being tracked yet.
@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 Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants