Open williamtheaker opened 1 month ago
For backward compatibility we can persist the behaviour for json
output and add GB
for humans. Going from int
s to float
s is definitely a breaking change and only useful for small Linux images so IMO we can skip it.
It would be easier to understand disk usage if the disk and VM size exposed by commands like
tart list
andtart get
were formatted with appropriate byte modifier.Current:
Reporting the disk allocation size as 51GB would be slightly easier to grok and match the behavior of similar tools like Docker and Podman:
For example, the base size of
ghcr.io/cirruslabs/debian:latest
is 1.4GB, but Tart reports it as "1," which is less precise.It might even be useful to rename Disk to something like "Allocated" since the current terminology can be kind of confusing.