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.

Sign up for GitHub

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

Jump to bottom

Nuclio needs to be pointed to use kaniko builder to work in k8s #8792

Open
2 tasks done
pratclot opened this issue Dec 8, 2024 · 1 comment
Open
2 tasks done

Nuclio needs to be pointed to use kaniko builder to work in k8s #8792

pratclot opened this issue Dec 8, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@pratclot
Copy link

pratclot commented Dec 8, 2024

Actions before raising this issue

  • I searched the existing issues and did not find anything similar.
  • I read/searched the docs

Steps to Reproduce

  1. Install the Helm chart with nuclio.enabled=true.
  2. Observe the cvat-nuclio-dashboard pod fail with: Cannot connect to the Docker daemon.

Expected Behavior

The dashboard shall either work right away, or an additional config option should be present in values.yaml.

Possible Solution

Add new values from official nuclio chart:

nuclio:
  dashboard:
    containerBuilderKind: kaniko

Context

Hey folks! I wanted to enable nuclio for my deployment in k8s, and it seems like the Helm chart does not support running it there (at least without Docker daemon). I added new values from nuclio docs and it seemed to have helped.

Environment

Just used `develop` branch at 12eec5481bb3d4e6219bb8214df524f27b3037e3.
@pratclot pratclot added the bug Something isn't working label Dec 8, 2024
@satyatejaswini1234
Copy link

The solution is to update the Helm chart or configuration to enable Kaniko as the builder, which resolves the issue of Docker access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pratclot @satyatejaswini1234