Could not open file fixtures/* about kubeval

[stephan-rayner]

This is still a thing that happens I ran into this about an hour ago. The folder naming trick is not bad but I think I may have something a little better. By using the -d flag you can specify the folder in the container, in this case I called it fixtures/.

docker run -it -v $PWD/Files/fixtures garethr/kubeval -d fixtures

I hope this helps someone 🙂

[TheKangaroo]

Figured this one out, the mounting won't work with different names.
(-v pwd/Files:/fixtures)
Since my local folder is called Files I changed the command to

docker run -it -v `pwd`/Files:/Files garethr/kubeval Files/*

But I'm not quite sure what's the problem here...

[garethr]

Mmmm, interesting. Glad you found a workaround for now. I'll try and recreate this when I get a moment and come back with any questions.

[garethr]

So I think the problem here is that the wildcard expansion happens locally, not inside the container. So this works when you have the same folder name, or rather it does with the shell you're using. Looking around this is more a limitation/how docker works. I'll close for now as I don't think this is something I can work around on my end.

[rufreakde]

if it is okay for you to go through the folders recursivly what worked for me was to use the following command instead:

kubeval  --directories ./templates/