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

BUG: init container -n flag required when outputting files format #270

Closed
daniel-butler-irl opened this issue Aug 2, 2019 · 2 comments · Fixed by #272
Closed

BUG: init container -n flag required when outputting files format #270

daniel-butler-irl opened this issue Aug 2, 2019 · 2 comments · Fixed by #272
Labels
bug Something isn't working

Comments

@daniel-butler-irl
Copy link

When using the following flags to start the init container I would expect it to mount the secrets as files

args: ["-e","/encrypted-secrets","-d","/decrypted-secret-files", "-f", "files"]

However, I get the following error:

Failed to run init container: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undef
ined

Adding the -n flag resolves the issue and correctly decrypts the files while ignoring the -n

args: ["-e","/encrypted-secrets","-d","/decrypted-secret-files", "-f", "files", "-n", "secrets.env"]
@omerlh omerlh added the bug Something isn't working label Aug 4, 2019
@omerlh
Copy link
Contributor

omerlh commented Aug 4, 2019

Thanks for reporting this! I find the bug and fixing it now

@omerlh
Copy link
Contributor

omerlh commented Aug 5, 2019

The new init container should be available on dockerhub, using the latest tag or 1.2.0 tag. Please let me know if you're bug wasn't solved.

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

Successfully merging a pull request may close this issue.

2 participants