Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix/fix disk space issues in GitHub #47816

Merged

Conversation

jscheffl
Copy link
Contributor

As we see disk space issues in v2-10-test builds... cherry-pick #46358 and #46428 to the maintenance branch,

jscheffl and others added 2 commits March 15, 2025 19:18
* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Triage disk space issues, DO NOT MERGE

* Move docker storage to second drive in general

* Cleanup debug and triaging stuff

* Exception of docker volume for constraints building
…e#46428)

The apache#46358 moved docker to another mounted directory - but this
directory and all files in it are owned by host user. The directory
and all files inside should be owned by root in order to properly
reflect permissions of the files when building docker images.

The change is now simplified. Rather than passing mount directory
by variable and passing it through GitHub Actions, we hard-code
the location of docker in cleanup_docker.sh script - we also
incorporate changing ownership and showing disk space in the same
cleanup_docker.sh script and make sure that script is only called
in the "real" (not composite) actions at the beginning - right
after the repository is checked out - previously that script
was also called in composite actions and changing the repo to be
writeable was done AFTER cleanup_docker.sh - which would not
work as we want the /mnt directory to be still owned by the
host user, but the docker storage should be still owned by root.
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM... Let's see what CI says

@jscheffl
Copy link
Contributor Author

Failures are unrelated to the fix, merging.

@jscheffl jscheffl merged commit 6d42cce into apache:v2-10-test Mar 15, 2025
52 of 58 checks passed
@gopidesupavan
Copy link
Member

cool seems v2 will be happy now :)

@jscheffl
Copy link
Contributor Author

cool seems v2 will be happy now :)

No, unfortunately some further fixes needed....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants