Some providers allow you to use custom images in place of the default OS image.
This is a double-edged sword.
Using a custom image can dramatically decrease the time it takes to deploy a server. It depends on what you pre-install on it of course.
If you use a custom image, it is only valid for one WPCD version and one web server type.
In other words, any image you create will be valid for, say, WPCD 5.0.0 and OpenLiteSpeed. You will not be able to create any NGINX servers until you remove the custom image from the provider settings OR you create a virtual provider without a custom image.
And, you will need to recreate the image for the next version of WPCD (major or minor).
If your custom image does not have anything to do with the WPCD 5.0 install (eg: you’re adding some other packages you need later or you just want to make sure your starting image has all the latest Os updates), then you will not have an issue.
But if you use a custom image based on an initial standard WPCD server installation, then these restrictions apply.
Each OS requires a different custom image.
Care must be taken that you provide the correct ID for each OS. Otherwise, you might end up deploying an Ubuntu 18.04 server when requesting an Ubuntu 22.04 server – we will not know the difference and will tag the server with 22.04. This will, as you might expect, cause all kinds of issues!
The following providers support custom images:
We have the ability to quickly add support for the following providers if it is a gating factor in your deployment:
Just open a support ticket and let us know if you need it. However, please do not ask us to add this feature to the above listed providers if you do not really need it!
If you are seeing weird or unexplained behavior with your servers, please remove the custom image ids from your settings area and try deploying the server with the default OS images.