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

kubeflow-pipelines-visualization-server missing wget #2920

Open
shanedell opened this issue Oct 28, 2024 · 0 comments · May be fixed by #2928
Open

kubeflow-pipelines-visualization-server missing wget #2920

shanedell opened this issue Oct 28, 2024 · 0 comments · May be fixed by #2928
Labels
needs-triage applied to all new customer/user issues. Removed after triage occurs.

Comments

@shanedell
Copy link

Which image/versions are related to this issue/feature request?

cgr.dev/chainguard/kubeflow-pipelines-visualization-server:latest

Issue/Feature description

When deploying Kubeflow using Kubernetes and replacing the visualization-server with the chainguard image, cgr.dev/chainguard/kubeflow-pipelines-visualization-server:latest. The error is caused by a liveness and readiness probe that both try using wget. Below is the error:

  Warning  Unhealthy  104s (x13 over 2m33s)  kubelet            Readiness probe failed: OCI runtime exec failed: exec failed: unable to start container process: exec: "wget": executable file not found in $PATH: unknown
  Warning  Unhealthy  104s (x5 over 2m33s)   kubelet            Liveness probe failed: OCI runtime exec failed: exec failed: unable to start container process: exec: "wget": executable file not found in $PATH: unknown

I believe it should be a simple fix of adding wget to

default = ["kubeflow-pipelines-visualization-server"]

@shanedell shanedell added the needs-triage applied to all new customer/user issues. Removed after triage occurs. label Oct 28, 2024
shanedell added a commit to shanedell/chainguard-images that referenced this issue Nov 14, 2024
- wget is needed for liveness and readiness probes.

Closes chainguard-images#2920
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage applied to all new customer/user issues. Removed after triage occurs.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant