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

Workaround occasional failures of docker system prune in public runners #38825

Merged

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Apr 8, 2024

Occasionally docker system prune fails on Public docker runners with

file resize error: truncate /var/lib/docker/buildkit/containerdmeta.db: read-only file system

This happens after docker has been already cleaned and should have no side efects if the metadata db could not be truncated.

Ignoring error in this case should allow the job to continue.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Occasionally `docker syetem prune` fails on Public docker runners with

file resize error: truncate /var/lib/docker/buildkit/containerdmeta.db:
read-only file system

This happens after docker has been already cleaned and should have no
side efects if the metadata db could not be truncated.

Ignoring error in this case should allow the job to continue.
@potiuk potiuk merged commit f50cc61 into apache:main Apr 8, 2024
15 checks passed
@potiuk potiuk deleted the workaround-occasional-read-only-filesystem branch April 8, 2024 09:33
ephraimbuddy pushed a commit that referenced this pull request Apr 16, 2024
…rs (#38825)

Occasionally `docker syetem prune` fails on Public docker runners with

file resize error: truncate /var/lib/docker/buildkit/containerdmeta.db:
read-only file system

This happens after docker has been already cleaned and should have no
side efects if the metadata db could not be truncated.

Ignoring error in this case should allow the job to continue.

(cherry picked from commit f50cc61)
ephraimbuddy pushed a commit that referenced this pull request Apr 16, 2024
…rs (#38825)

Occasionally `docker syetem prune` fails on Public docker runners with

file resize error: truncate /var/lib/docker/buildkit/containerdmeta.db:
read-only file system

This happens after docker has been already cleaned and should have no
side efects if the metadata db could not be truncated.

Ignoring error in this case should allow the job to continue.

(cherry picked from commit f50cc61)
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.

2 participants