Import your own custom Image


In the E2E cloud stack, we empower our customers by allowing them to get their customized images made available in their myaccount console. Customers can bring in their golden images (customized Linux distributions with software and configurations to fit the specific needs) from the on-premises environment or even from other cloud providers to the E2E cloud platform and use them to create virtual machines with their choice of Plans. | The option saves time and effort required to set up and configure your node right from the scratch again to get your required golden stack in place. You can get your bootable disk images from virtual machines (VMs) on your local workstation, from your physical datacenters, or from VMs that run on another cloud platform to E2E Cloud-Platform.


VM initialization method

There are different methods to pass information to a newly created Virtual Machine. This information can be the network configuration of the VM, user credentials, init scripts, and free form data.

In our cloud platform, we use the OpenNebula context package for virtual machine initialization, which configures the network, sets the user credentials, sets hostname, adds provided SSH keys, etc.

Download and Installation of Contextualization Packages and Dependencies to your VM

CentOS/RHEL 6.x
# wget
# yum install -y epel-release
# yum install -y one-context-[0-9]*el6*rpm
CentOS/Fedora/RHEL 7.x
# wget
# yum install -y epel-release
# yum install -y one-context-[0-9]*el7*rpm
# wget
# apt-get purge -y cloud-init
# dpkg -i one-context_*deb || apt-get install -fy
OpenSUSE 42,15
# wget
# zypper --no-gpg-check install -y one-context-[0-9]*suse*rpm
Alpine Linux
# wget
# apk add --allow-untrusted one-context-[0-9]*apk
FreeBSD 11,12
# wget
# pkg install -y curl bash sudo base64 ruby open-vm-tools-nox11
# pkg install -y one-context-[0-9]*.txz


If you have cloud-init present in your virtual machine for initialization, please make sure that the respective cloud-init service is disabled on boot before taking the image. The cloud-init will conflict with the OpenNebula context package which may result in failure of virtual machine initialization process.

Supported image formats

E2E cloud-platform supports images in qcow2, qed, raw, vdi, vhd, and vmdk formats for import.


To save space and reduce import time you can also compress the file using gzip and tar compression formats.

Disk requirements

The image should contain single disk partition. The primary partition on the disk can be in any format that you like as long as it boots properly from the MBR bootloader. The disk should not be larger than 2048 GB (2 TB).

Operating System requirements

Disk images with any bootable operating system can be imported to E2E cloud-platform, but the context package and intialization method are easier to configure for the Operating systems offered on virtual node environment than others.
The following operating systems are tested for this guide:
  • CentOS/RHEL >= 6

  • Debian >= 8

  • Ubuntu >= 14.04


Other operating systems can also be imported but they might require additional configuration steps that are not covered in this guide.

Importing an image to E2E Cloud-Platform

Once you have an image ready meeting the aforementioned prerequisites, you can provide us with a downloadable link from where we can download the image file. We will get the image file imported to our cloud-platform from the backend and make it available in your myaccount Saved Images section from where you can use it to create virtual machines with your choice of plan.
  • Go to MyAccount and log in using your credentials set up at the time of creating and activating the My Account.

  • On the left Navigation bar, Select Compute available under the product section.

  • You will redirect to the Manage Node page.

  • Click on the ‘Saved Image’.

  • You will redirect to the ‘Manage Saved Image’ page.

  • Click on the ‘Import Custom Image’.

  • The import custom image window will be opened. Please provide the following details.



The imported image will be saved in a format specific to our environment. This means that the actual size of the image stored in our system can be different from the size of the image as visible in your environment. This difference can sometimes be as high as 5 times the original size. Please contact us at

Public URL: Enter the URL (downloadable link) of the image you want to use in this text field. We will import the image file from a specified link.


You can upload your image to the file-sharing tool and make the file public like Dropbox. Make sure the URL ends in the file extension (like instead of

Custom Image Name: This field is pre-filled with the name, but you can customize it if you like to use it to import a custom saved image.

  • After you’ve entered the required details, click Import. An information message will appear on screen.



Importing virtual images will take some time. It’s depending upon the size of an image. You will be notified once an image is imported.

  • Once your custom image is added to your account, you can create a node or create a scale group from your custom image.



There is no charges for importing your custom images on E2E Cloud-platform. You will be charged for the storage space consumed by the image at ₹ 4.00/GB per month.
You can create the virtual machine using your imported custom image and delete the image to avoid incurring image storage costs.