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

Difficulties descending into nested chart directories for dependencies #46

Open
beacomni opened this issue Apr 22, 2020 · 1 comment
Open

Comments

@beacomni
Copy link

When pulling a dependent chart, helm snyk test seems to not be able to descend into dependency directories. The example I'm using was

helm pull sumologic/sumologic --untar=true --untardir=sumologic_sumologic

I then do:

:~$ helm snyk test sumologic_sumologic/sumologic/

try to run 'helm template sumologic_sumologic/sumologic/' first!
ubuntu@ip-10-42-75-92:~$ ls sumologic_sumologic/sumologic/

there is a Chart.yaml in the directory noted already:

:~$ ls sumologic_sumologic/sumologic/
charts  Chart.yaml  conf  requirements.lock  requirements.yaml  sumologic_sumologic_prometheus_operator_kube_state_metrics.txt  templates  values.yaml

Descending into the dependency directory, does work however:

helm snyk test sumologic_sumologic/sumologic/charts/falco/

Perhaps this is more of a feature request, though I feel the inability to deal with chart dependencies should be noted in Readme. However, I think since I get an error message with the top level chart, the tool may still be missing images that are in the top level chart.

@jcogilvie
Copy link

Hi from sumo.

This isn't actually an issue with dependencies; it has to do with chart size. The child process that is spawned to run helm has a default buffer size of 1024*1024 and that's too small. I bumped it up to 1024x the default to see what would happen, and a large sumo chart passed that stage of the build (but failed further along).

const res: ChildProcess = exec(fullCommand, { maxBuffer: 1024*1024*1024 },(err: ExecException | null, stdout: string, stderr: string) => {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants