This may be tricky to do, and may indeed be something we don't even want to do.

The "base-size" of snapshots created by containerd is 10gb, basically meaning all root volumes attached to microvms will be able to expand up to a max of 10gb. When using with docker most users would end up just attaching additional volumes and using those instead so most did not care about the rootfs size.

[plugins]
  [plugins."io.containerd.snapshotter.v1.devmapper"]
    pool_name = "flintlock-thinpool"
    root_path = "/var/lib/containerd/snapshotter/devmapper"
    base_image_size = "10GB"
    discard_blocks = true

In our case, it is easier to say at the flintlock level that users can "just" supply an additional volume if they need more room, but it it less pleasant at a capmvm level.

being able to override this and expand an indivdual snapshot size for an mvm would be better, but idk if containerd lets us do this.

we could resize the disk after mvm creation

or make the additional volume option easier to use (also right now i dont think additional volumes are actually mounted in and the user has to do it after the fact)

Setting root_volume.size_in_mb seems to have no effect #553

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions