[v3-2-test] Fix CARGO_HOME location for airflow user builds (#64899)#64914
Merged
[v3-2-test] Fix CARGO_HOME location for airflow user builds (#64899)#64914
Conversation
Move CARGO_HOME from /usr/local/cargo to /home/airflow/.cargo so that cargo builds work correctly when running as the airflow user, avoiding permission issues with the system-wide cargo directory. (cherry picked from commit e62a12d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496 and
jscheffl
as code owners
boring-cyborg
bot
added
the
area:production-image
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Move CARGO_HOME from /usr/local/cargo to /home/airflow/.cargo so that cargo builds work correctly when running as the airflow user, avoiding permission issues with the system-wide cargo directory. (cherry picked from commit e62a12d)
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.