Skip to content

enter: don't filter environment variables with special characters#1858

Open
cshuaimin wants to merge 1 commit into89luca89:mainfrom
cshuaimin:push-wtxyqquwxuot
Open

enter: don't filter environment variables with special characters#1858
cshuaimin wants to merge 1 commit into89luca89:mainfrom
cshuaimin:push-wtxyqquwxuot

Conversation

@cshuaimin
Copy link
Copy Markdown

Fix #1842

Docker and Podman support only specifying env names, but seems lilipod doesn't. I'm not sure how to deal with lilipod, should I add an if condition?

@dottorblaster
Copy link
Copy Markdown
Collaborator

I would ask @89luca89 😅 I think lilipod should support this upstream but at the same time I don't want to add a huge burden on top of @89luca89's shoulders.

@dottorblaster
Copy link
Copy Markdown
Collaborator

@cshuaimin it looks like the formatter is failing, could you fix it? ❤️

@cshuaimin
Copy link
Copy Markdown
Author

Hi @dottorblaster I fixed formatting.
I agree that supporting in lilipod should be better solution than adding an if branch. I can also create a PR to lilipod.

Previously when passing environment variables from the host to the
container, the script filtered out any variables that contained special
characters. This could lead to important environment variables being
omitted when entering the container.
In this commit, I modified it to only pass the names of the environment
variables to the --env flag, rather than their full key-value pairs, and
let container runtime read the values.
I also changed printenv to separate lines with null characters to avoid
issues with newlines in variable values.
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

Successfully merging this pull request may close these issues.

distrobox-enter: envs with " are not present in container

2 participants