Dockerfile.dapper: set $HOME properly #9090
Merged
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.
$HOME
refers to$DAPPER_SOURCE
, which is set in the same expression and is thus not visible at the time of substitution.This problem is not immediately visible with Docker, Inc.'s docker merely because it resets an unset
$HOME
to/root
(but still breaking the Go cache). Under podman, this problem is immediately visible because an unset$HOME
remains unset and subsequently breaks thego generate
invocation.Types of Changes
Bug fix — build system
Verification
Run
make generate
under podmanTesting
N/A — build system
Linked Issues
make generate
fails under podman due to unset$HOME
, and is subtly broken under docker #9089User-Facing Change