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

Services running out of disk space when pulling images on autoscaled machines #6990

Open
GitHK opened this issue Dec 23, 2024 · 0 comments
Open
Assignees
Labels
bug buggy, it does not work as expected High Priority a totally crucial bug/feature to be fixed asap

Comments

@GitHK
Copy link
Contributor

GitHK commented Dec 23, 2024

Services running on autoscaled machines run out of disk space when are being opened and fail to start.

Something similar to the following error communicating that disk space ran out.

"2024-12-23T08:15:55.593Z","ip-10-0-3-149","dy-sidecar_a2a82999-1c8d-4cfe-b081-41c6a587366b.1.vtsax3o9cnggg3fv9ql1d37av","log_level=ERROR | log_timestamp=2024-12-23 08:15:55,593 | log_source=servicelib.docker_utils:pull_image(253) | log_uid=None | log_msg=Unexpected error while validating 'pull_progress={'errorDetail': {'message': 'failed to register layer: write /usr/sbin/wipefs: no space left on device'}, 'error': 'failed to register layer: write /usr/sbin/wipefs: no space left on device'}'. TIP: This is probably an unforeseen pull status text that shall be added to the code. The pulling process will still continue.

NOTE

It is possible for the error to also occur when pulling inputs the state or the outputs!

After asking the user to start their service again the service was able to start. It was running on a machine with 873.3 Gb Free space.


What I think it happened

I can think of the possible situation:

  1. a machine with lower disk space is used and the service does not fit
  2. the disk space on a previously used machine ran out
  3. a mix of 1 and 2
@GitHK GitHK added the bug buggy, it does not work as expected label Dec 23, 2024
@GitHK GitHK added the High Priority a totally crucial bug/feature to be fixed asap label Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug buggy, it does not work as expected High Priority a totally crucial bug/feature to be fixed asap
Projects
None yet
Development

No branches or pull requests

3 participants