feat: show used / max RAM per remote container#22
Merged
Conversation
The remote compact rows showed only used memory; now they show the full "used / limit" from docker stats (the limit = the container's RAM cap, i.e. its max), matching the local containers panel. Verified at narrow widths — fits on the line, no truncation/crowding. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The remote compact rows showed only used memory; now they show the full
used / limitfromdocker stats— the limit being the container's RAM cap (its max), matching the local containers panel (48.03MB / 66.56GB).e.g.
0.18% · 79.86MiB / 256MiB,autonomy-ev-ops 0.07% · 73.16MiB / 1GiB.Screenshot-verified at 1180px and 1000px (narrow sidebar): fits on the line, no truncation or crowding.
🤖 Generated with Claude Code