Disk size is fixed to image size when deploying a custom image.

We generally want the disk to be extended automatically when deploying new instances.

This way we could immediate boot a custom image and be ready to use. Otherwise it would require an additional step to resize it, wait for it to complete, then finally boot that instance.

Which requires additional status requests to monitor the resize progress.

So my question is: Using the API, without additional resizing request, is there a way to define the preferred disk size of that new instance on instance creation?

1 Reply

Hello @471C-B0AE,

That's a great question! I wanted to let you know that our team is aware of this issue and that we are working to release a fix for this in the near future. Thanks for your patience in the meantime.

Kind regards,
Joe C.
Linode Support Team

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct