`limactl list`: dynamically reduces the column, depending on the terminal width

[AkihiroSuda]

• limactl list: add "VMTYPE" column #1203

We are going to have too many columns:

$ limactl ls
NAME       STATUS     SSH            VM TYPE    ARCH      CPUS    MEMORY    DISK      DIR
default    Stopped    127.0.0.1:0    qemu       x86_64    4       4GiB      100GiB    /Users/suda/.lima/default
vz         Stopped    127.0.0.1:0    vz         x86_64    4       4GiB      100GiB    /Users/suda/.lima/vz

When the terminal is small, some columns (especially "DIR") can be just hidden.

[jandubois]

One thing we could do to save some small amount of space would be to replace $HOME in "DIR" with ~:

$ limactl ls
NAME       STATUS     SSH            VM TYPE    ARCH      CPUS    MEMORY    DISK      DIR
default    Stopped    127.0.0.1:0    qemu       x86_64    4       4GiB      100GiB    ~/.lima/default
vz         Stopped    127.0.0.1:0    vz         x86_64    4       4GiB      100GiB    ~/.lima/vz

[jandubois]

Another idea: check if all instances use the native arch (which I suspect will be true for most users), and drop the "ARCH" column if there are no emulated instances.

[AkihiroSuda]

~

Yes, already opened a PR

• limactl list: "/Users/<USERNAME>/.lima/..." -> "~/.lima/..." #1205

[AkihiroSuda]

Another idea: check if all instances use the native arch (which I suspect will be true for most users), and drop the "ARCH" column if there are no emulated instances.

SGTM

[afbjorklund]

Some of these could probably be delegated to a "wide" option, ilke in kubectl ?

It would show all the columns, even if some of them are being hidden by default.

Probably my fault, for wanting to show resources (cpu/mem/disk) by default...

• c908af7

But I never found out what the "SSH" column is used for ? only has port, not key etc

[afbjorklund]

drop the "ARCH" column if there are no emulated instances

Can do the same for vmtype, perhaps ? Hide it, if identical.

Especially if there is only one vmtype available, like on Linux.

[afbjorklund]

If evaulating which columns should be visible, one that could be useful is the containerd version...

Could be adopted to show some other version, like docker version or podman version, as discussed.

This was just when comparing the output of docker-machine and lima ("containerd-machine"):

$ docker-machine ls
NAME      ACTIVE   DRIVER   STATE     URL                     SWARM   DOCKER      ERRORS
default   *        qemu     Running   tcp://127.0.0.1:44729           v20.10.12   

$ limactl ls
NAME       STATUS     SSH                VMTYPE    ARCH      CPUS    MEMORY    DISK      DIR
default    Running    127.0.0.1:60022    qemu      x86_64    4       4GiB      100GiB    ~/.lima/default

That "active" thing is just comparing the $DOCKER_HOST, it would here be the $LIMA_INSTANCE.