Review the Vultr Marketplace technical requirements your application image must meet before building, with helper scripts from the Vultr GitHub repository.
Vultr Marketplace has technical requirements your application must meet before you build an image. Our GitHub repository also has helper scripts and examples.
This guide explains how to meet these requirements before building an image.
Your application must meet the following requirements:
When a customer deploys a Marketplace app, Vultr can expand your app to fill the filesystem but cannot shrink it. Use the marketplace-2c-2gb plan, which is designed for Marketplace applications. This plan includes 2 vCPUs, 2 GB of memory, and 8 GB of storage.
If you create a 20 GB Marketplace app, and the customer deploys an 80 GB subscription, Vultr expands the app to fill the entire 80 GB filesystem. However, if you create an app with an 80 GB filesystem, customers cannot deploy the app on smaller Vultr instances. Use the smallest possible filesystem for your app.
Vultr Marketplace uses cloud-init to initialize the instance with network addresses, passwords, and startup scripts. These operating systems have the correct version of cloud-init preinstalled if you use Vultr's images.
Canonical added support for Vultr in cloud-init version 21.2. Until this version is available in your OS repository, install Vultr's cloud-init. See the install_cloud_init() function in our helper script on GitHub.
Install Vultr's cloud-init package as follows.
Change to the /tmp directory.
Download the cloud-init package.
Install the package.
Debian systems must use this version. Do not compile from source or install from the Debian repositories.
Change to the /tmp directory.
Download the cloud-init package.
Refresh the package index.
Install the package.
Ubuntu systems use the universal build.
Change to the /tmp directory.
Download the cloud-init package.
Refresh the package index.
Install the package.
Cloud-init may not correctly interface with NetworkManager on some distributions, such as CentOS and RHEL. On these distributions, the network is not configured correctly, and the boot process fails. If this occurs, disable NetworkManager, then install and enable the network-scripts package. NetworkManager must be disabled but does not need to be uninstalled.
The Marketplace requires the kernel option vultr on Bare Metal instances. The option is not required for cloud deployment, but including it keeps your application compatible with both VPS and Bare Metal deployments. If your application is based on one of Vultr's OS images, this kernel option may already exist.
Check /etc/default/grub.
You may see vultr in the output:
If there is no vultr option, add it.
Edit /etc/default/grub.
Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT and add vultr to the end.
Save the file and close the editor.
Update GRUB. Check the documentation for your distribution to determine the correct procedure. Ubuntu and Debian systems may use the update-grub utility.
On CentOS and RHEL systems, add the kernel option with grubby.
0 Comments
Be the first to comment and share your perspective with the community.