[
https://issues.apache.org/jira/browse/HADOOP-14026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840090#comment-15840090
]
Allen Wittenauer commented on HADOOP-14026:
-------------------------------------------
bq. the current user name can contains some not english characters and upper
letters (after all this is usually the name/nickname of the owner)
http://unix.stackexchange.com/questions/76354/who-sets-user-and-username-environment-variables
is a quick link to provide more info, but the sum of it is that $USER is
almost always set to the user's login name via the login(1) process. I
honestly can't remember the last time I saw a system that didn't do that. Now
there are cases where $USER isn't set (e.g., didn't go in through login), and
the appropriate response is to set $USER to the name (e.g., output of id -u -n).
What is your environment that this is not true?
> start-build-env.sh: invalid docker image name
> ---------------------------------------------
>
> Key: HADOOP-14026
> URL: https://issues.apache.org/jira/browse/HADOOP-14026
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Gergő Pásztor
> Assignee: Gergő Pásztor
> Attachments: HADOOP-14026_v1.patch
>
>
> start-build-env.sh using the current user name to generate a docker image
> name. But the current user name can contains some not english characters and
> upper letters (after all this is usually the name/nickname of the owner).
> Both of them are not supported in docker image names, so the script will fail.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
