-
Notifications
You must be signed in to change notification settings - Fork 189
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
Figure out which container is consuming all available disk space #3571
Labels
Comments
humphd
added
type: bug
Something isn't working
area: deployment
Production or Staging deployment
labels
Apr 30, 2022
Running everything locally, I see:
If you scroll that all the way to the right, you can see the total size of the containers. Notice:
Everything else is tiny. I'll let this run for a while and see what it does. It would be interesting to see this same data for staging/prod. |
staging:
production:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
From @manekenpix on Slack:
I did a quick scan through the containers on Portainer, and I can't figure it out. For example, going to https://dev.portainer.telescope.cdot.systems/#!/1/docker/containers/b01f331167b374581f7c56b2cf7ae17a47d8887d6bbbbda6c891fb803ff98687/stats shows the CPU, Memory, Network and I/O usage for the rss-bridge service. Each container can show you the same.
None of the ones I looked at showed any significant disk I/O.
The text was updated successfully, but these errors were encountered: