Skip to content

Conversation

@chromy
Copy link

@chromy chromy commented Jan 19, 2026

An error at least @runningcode and I have encountered is colima running out of disk space.
This adds a devenv doctor check to suggest a resolution to the dev.

@chromy chromy force-pushed the chromy/2026-01-19-check-disk-space branch 2 times, most recently from bd3355a to 7ff5777 Compare January 19, 2026 11:48
@checker
def check() -> tuple[bool, str]:
status = colima.check()
if status != colima.ColimaStatus.UP:
Copy link

@runningcode runningcode Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what the Colima status was when this happened. I assume this exits early if colima reports that it is up?

Copy link

@runningcode runningcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just had one question on the PR

@joshuarli joshuarli force-pushed the chromy/2026-01-19-check-disk-space branch from 7ff5777 to 68e62b3 Compare January 26, 2026 20:04
Copy link
Member

@joshuarli joshuarli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

colima VM's disk is copy-on-write, so even if you resize the disk to some higher amount it's likely the host disk runs out before your VM disk free % detection works

it'll be better to initially provision a large disk equal to the host's disk then simply check the host's disk free rather than the VM's

i'll rework this PR!

@joshuarli
Copy link
Member

superseded by #219

@joshuarli joshuarli closed this Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants