Great question here. It looks like you deployed a micro VM (the current default in the mainnet playground). Micro VMs get their root filesystem added in such a way that it doesn’t show up as a block device, and thus doesn’t appear in the
lsblk output. What you’re seeing there is the configuration disk which is mounted temporarily when the VM starts up to inject your SSH key.
df to see file systems and their usage, with the
-h flag for “human readable” quantity labels. Here’s an example from one of my micro VMs:
# df -h
Filesystem Size Used Avail Use% Mounted on
dev 229M 0 229M 0% /dev
run 235M 152K 235M 1% /run
tmpfs 235M 0 235M 0% /dev/shm
/dev/root 477G 284M 476G 1% /
Now, I only allocated 500mb for the root file system, but it shows an available space of 476gb. The reason for this is that we’re actually seeing the full size of the underlying drive in the 3Node, rather than our disk quota for this particular VM. It’s just a limitation of micro VMs for now. I have an open issue to show the quota size instead, but devs aren’t prioritizing it at this time. Anyway, I can compare the used figure from
df to the amount I specified at deployment and know that I have about 215mb of free space.
When it comes to full VMs, this is not an issue, since they use an attached virtual disk for the root file system which is seen properly both by
df. Full VMs also come with features like
systemd and a full kernel, which make them more compatible with workflows intended for a VPS or bare metal Linux installation.
Micro VMs can still do a lot, but if you want test a full VM, they are available in the testnet playground or can be deployed through the mainnet playground with a few extra steps.