[build] Fix HOME environment in deploy-gitpod action #21252
Merged
+4
−0
Conversation
This file contains hidden or 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
GitHub Actions sets HOME=/github/home when running in a container, but this directory doesn't exist in the dev-environment image. This causes previewctl install-context to fail when generating SSH keys. Restore HOME=/home/gitpod to match the original Docker-based action behavior from before commit 80317ca. Co-authored-by: Ona <no-reply@ona.com>
corneliusludmann
approved these changes
Jan 13, 2026
geropl
added a commit
that referenced
this pull request
Jan 13, 2026
The previous fix (#21252) only applied HOME=/home/gitpod to the 'Deploy Gitpod' step, but the 'Install previewctl' step runs first and also needs the fix. Leeway fails with 'getwd: no such file or directory' when HOME points to a non-existent directory. Validated locally: docker run --rm --user root -e HOME=/github/home ... leeway run dev/preview/previewctl:install # Fails: getwd: no such file or directory docker run --rm --user root -e HOME=/github/home ... export HOME=/home/gitpod leeway run dev/preview/previewctl:install # Succeeds Co-authored-by: Ona <no-reply@ona.com>
geropl
added a commit
that referenced
this pull request
Jan 13, 2026
The previous fix (#21252) only applied HOME=/home/gitpod to the 'Deploy Gitpod' step, but the 'Install previewctl' step runs first and also needs the fix. Leeway fails with 'getwd: no such file or directory' when HOME points to a non-existent directory. Validated locally: docker run --rm --user root -e HOME=/github/home ... leeway run dev/preview/previewctl:install # Fails: getwd: no such file or directory docker run --rm --user root -e HOME=/github/home ... export HOME=/home/gitpod leeway run dev/preview/previewctl:install # Succeeds Co-authored-by: Ona <no-reply@ona.com>
geropl
added a commit
that referenced
this pull request
Jan 13, 2026
The previous fix (#21252) only applied HOME=/home/gitpod to the 'Deploy Gitpod' step, but the 'Install previewctl' step runs first and also needs the fix. Leeway fails with 'getwd: no such file or directory' when HOME points to a non-existent directory. Validated locally: docker run --rm --user root -e HOME=/github/home ... leeway run dev/preview/previewctl:install # Fails: getwd: no such file or directory docker run --rm --user root -e HOME=/github/home ... export HOME=/home/gitpod leeway run dev/preview/previewctl:install # Succeeds Co-authored-by: Ona <no-reply@ona.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
previewctl install-contextfails withexit status 1when generating SSH keys because the HOME directory doesn't exist.Root Cause
Commit 80317ca converted
deploy-gitpodfrom a Docker-based action to a composite action. The old Docker action explicitly setexport HOME=/home/gitpod, but the composite action inherits GitHub Actions' defaultHOME=/github/home, which doesn't exist in the container.Validation
Tested locally with the dev-environment container:
Solution
Restore
export HOME=/home/gitpodin the deploy-gitpod action to match the original Docker-based action behavior.