You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
When using proxmox clone allow the ability to resize existing disks after the clone
Use Case(s)
When using packer we typically want to perform updates, install new software, ect... this can require more disk space then the existing VM template has. Currently one has to pre-grow the template disks first which depending on the storage format could cause a bunch of extra space usage for no reason.
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
When using proxmox clone allow the ability to resize existing disks after the clone
Use Case(s)
When using packer we typically want to perform updates, install new software, ect... this can require more disk space then the existing VM template has. Currently one has to pre-grow the template disks first which depending on the storage format could cause a bunch of extra space usage for no reason.
Potential configuration
Potential References
The text was updated successfully, but these errors were encountered: