-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
fix(exec): Whitelist LC_ALL and LANG #5239
fix(exec): Whitelist LC_ALL and LANG #5239
Conversation
Can you explain this more? We need to pass env vars to child process but not to Docker itself via |
I thought, pipenv pass them to Docker already and we should do for all. Well, here we have two options: (1) extend basic vars with |
Thanks, I understand better. I wonder if they’re only needed for child process when using global binary source. In which case, they should be safe to include on the default whitelist. If they’re needed inside the container then we should build them into the container if not already |
By the way, I doubt |
I suspect there were only needed for binarySource=global. Let's add them to our whitelisted env vars for child process and not pass them into the container itself. |
🎉 This PR is included in version 19.112.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Ref #5062