[
https://issues.apache.org/jira/browse/HADOOP-15096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048469#comment-18048469
]
ASF GitHub Bot commented on HADOOP-15096:
-----------------------------------------
github-actions[bot] commented on PR #311:
URL: https://github.com/apache/hadoop/pull/311#issuecomment-3700916487
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> start-build-env.sh can create a docker image that fills up disk
> ---------------------------------------------------------------
>
> Key: HADOOP-15096
> URL: https://issues.apache.org/jira/browse/HADOOP-15096
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 3.1.0
> Reporter: Addison Higham
> Priority: Major
>
> start-build-env.sh has the potential to build an image that can fill up root
> disks by exploding a sparse file.
> In my case, the right ingredients are:
> Ubuntu 17.04
> Docker 17.09.0
> AUFS storage driver
> userId and groupid with a high number
> This happens when building the hadoop-build-${USER_ID} image, specifically in
> the
> {noformat}
> RUN useradd -g ${GROUP_ID} -u ${USER_ID} -k /root -m ${USER_NAME}
> {noformat}
> command.
> The reason for this:
> /var/log/lastlog is a sparse file that pre-reserves based on highest seen UID
> and GID, in my case, those numbers are very high (above 1 billion). Locally,
> this result in a sparse file that reports as 443 GB. However, under docker
> and specifically AUFS, it appears that his file *isn't* sparse and it tries
> to allocate the whole file.
> If you start this script and walk away to wait for it to finish, you come
> back to a computer with a completely full disk.
> Luckily, the fix is quite easy, simply add the `-l` option to useradd which
> won't create those files
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
