dustymabe added a new comment to an issue you are following:
Oh man yes you're right, the "no growpart on boot"
would be a huge regression here. Which actually gets us into a big mess...maybe we could
split out lvm-rootfs-growpart from container-storage-setup?
There are several ways to handle this. cloud-init has growpart functionality (which I
think we disable) and so does docker container-storage-setup. We could disable the
docker-storage-setup growpart and enable the cloud-init one (and then the user can disable
that one if he/she pleases).
Multiple ways to do it, let's find the way that makes the most sense and is
straightforward for the user.
To reply, visit the link below or just reply to this email