Don't write HOME env variable #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading HOME variable breaks multi-user container (i.e. logging as postgres user) if you try to load variables via `/etc/container_environment.sh`.
|
Yes, good point. Could you also exclude USER, UID, GID, GROUP and SHELL? |
|
Updated. |
|
I think it's not right. You call |
|
You're right - fixed. |
FooBarWidget
added a commit
that referenced
this pull request
Jun 20, 2014
Don't write HOME env variable
|
Thanks for the patch. |
guedressel
pushed a commit
to protosrc/baseimage-docker
that referenced
this pull request
Oct 31, 2017
Don't write HOME env variable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Loading HOME variable breaks multi-user container (i.e. logging as postgres user) if you try to load variables via
/etc/container_environment.sh.