Verify enough resources for Docker

[edithturn]

This PR is to fix the one that was merged: #20763
Point:
The runners have different filesystems to check the disk available. The one that is mounted should be taken to extract data of the disk available in the runners.

Please keep in mind it is a work in progress this is Work in Progress, and for now, I am printing "df -h" on the runner.

Close: #20251

[potiuk]

I think this is a different change ?

[edithturn]

@potiuk I am checking this data in the runner:

[potiuk]

You won't see it because you are not committer :). I will have to push it

[potiuk]

You will be able to see it here: #20959

[potiuk]

BTW. @edithturn When you create a PR you can create it as draft (not very well visible drop-down next to "create Pull Request" button if you want to do something for test - no need to prefix things with [WIP] . You can also convert it to draft and back any time via "convert to draft" link (or "Ready for Review" button). I will convert it to draft now.

[edithturn]

@potiuk I was wondering how to make it to avoid notifying others, thank you so much! 🙏🏼

[edithturn]

@potiuk I fixed it. I am considering, the mount point:
you can see it here: https://github.com/apache/airflow/runs/4871033753?check_suite_focus=true#step:7:90

# Disk current available partition_usage = psutil.disk_usage('/') disk_available = round(get_size(partition_usage.free))

Also, I rounded the value.

[potiuk]

FYI @edithturn : I am running it in my PR to check if it will also work for committers: #20959

[edithturn]

Thank you so much @potiuk, I also sent the last test, it takes time, especially the one which build the image.

[edithturn]

What defines a "committer"?

[potiuk]

What defines a "committer"?

This list:

airflow/.github/workflows/ci.yml

Line 96 in c135581

"BasPH",

[edithturn]

What defines a "committer"?

This list:

airflow/.github/workflows/ci.yml

Line 96 in c135581

"BasPH",

I see you have elevated privileges for Github events, right?
Are there things you can see in CI's processes that we can't?

[potiuk]

Are there things you can see in CI's processes that we can't?

Nope. It's just where the builds are run. There is no difference in what we see.

[edithturn]

I am running it in my PR to check if it will also work for committers: #

@potiuk this is the result on your runner. I also checked the one I sent, it finished successfully: https://github.com/apache/airflow/actions/runs/1724358952

let me know what are you thoughts

[potiuk]

Careful 🎉 :)

[potiuk]

🤞

[edithturn]

🤞🏼

[edithturn]

I think it worked! https://github.com/apache/airflow/runs/4886367996?check_suite_focus=true 👀