Skip to main content

Manage image

Using pre-configured images, you can swiftly launch an instance by selecting the desired operating system and applications as a template.

View image list

Check the list of images which is currently in use and its information.

  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.

  2. In the Image menu, see the current list of images in use.

    image. Image List Screen Default image list

    TypeDescription
    DefaultImages provided by default by KakaoCloud
    My ImageImages directly created by the user
    - Image name and description can be modified or deleted.
info

Windows-based images are not eligible for free credits among the available default images.

Create my image

Create an image of the current state of an instance.

info

Only the root volume with the operating system installed can be created as an image. For backing up additional volumes, please use snapshot feature.

  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.

  2. In the Instance menu, select Create image from the [More] icon.

  3. Enter the required information and click the [Create] button.

    image. Create image Create image

Create instance with my image

Create an instance using the information stored in My Image.

  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.
  2. Move to the Image menu and select the My image tab.
  3. Select Create instance of an image.
  4. Enter the required information and click the [Create] button.

Modify my image

Modify the image you have created.

info

For images shared from other projects, only the creator of the image can modify them.

  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.
  2. Move to the Image menu and select the My image tab.
  3. Select Modify image from the [More] icon.
  4. Modify the information and click the [Save] button.

Share my image

Share an image you created with other projects you are part of.

info
  • Only the user who initially created the image can share and unshare the image.
  • Members of the project that have received the image will see a [Shared] icon next to the shared image.
  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.

  2. Move to the Image menu and select the My image tab.

  3. Select Share image from the [More] icon.

  4. Select the project to share with and click the [Share] button.

    image. Share Image Share image

Delete my image

Delete images that are no longer in use.

info

For images shared from other projects, only the creator of the image can delete them.

  1. Go to Beyond Compute Service > Virtual Machine in the KakaoCloud Console.
  2. Move to the Image menu and select the My image tab.
  3. Select Delete image from the [More] icon.
  4. In the popup window, enter the name of the image and click the [Delete] button.

Change Root volume partition table format

Instances based on certain operating systems have a default partition table format of the root volume disk as MBR (Master Boot Record). The MBR partitioning scheme supports up to 4 partitions and works on disks of up to 2.0TB, but the GPT partitioning scheme has no limit on the number of partitions or capacity.
KakaoCloud provides cloud images for each operating system without changing their settings. You are able to change the Root volume partition table format (MBR) of instances based on CentOS, CentOS Stream, and Rocky Linux OS currently provided by KakaoCloud to the GPT (GUID Partition Table) system..

The partition table format and file system type provided by KakaoCloud for each operating system are as follows:

OS nameVersionRoot volume partition table format
Ubuntu20.04GPT
Ubuntu22.04GPT
Ubuntu24.04GPT
CentOS Stream9MBR
Rocky Linux8.10MBR
Rocky Linux9.4MBR
Alma Linux8.10GPT
Alma Linux9.4GPT
Windows2019MBR
Windows2022MBR

Procedure

The following is to change the disk partition table format from MBR to GPT for a CentOS instance.
This procedure is based on the CentOS Stream 8 image provided by KakaoCloud.

caution

When changing the partition table format of an existing volume, please pay attention to data preservation. It is recommended to back up before making any changes.

  1. Use the lsblk command to check the current disk information.

    lsblk command
    [root@centos ~]$ sudo fdisk -l

    Disk /dev/vda: 10.7 GB, 10737418240 bytes, 20971520 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: dos
    Disk identifier: 0x0009b542

    Device Boot Start End Blocks Id System
    /dev/vda1 * 2048 20971486 10484719+ 83 Linux
  2. Check the partition table information of the current disk using the gdisk command.

    gdisk command
       [root@centos ~]$ sudo gdisk -l /dev/vda
    GPT fdisk (gdisk) version 0.8.10

    Partition table scan:
    MBR: MBR only
    BSD: not present
    APM: not present
    GPT: not present

    ************************************************** *************
    Found invalid GPT and valid MBR; converting MBR to GPT format
    in memory.
    ************************************************** *************

    Disk /dev/vda: 20971520 sectors, 10.0 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 79C4C601-BF62-45E4-97F8-AB21F158EED7
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 20971486
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)

    Number Start (sector) End (sector) Size Code Name
    1 2048 20971486 10.0 GiB 8300 Linux filesystem
  3. Change the partition table from MBR to GPT using the gdisk command.

    • GPT requires a boot partition, so create that partition.

    • Set the boot partition as first sector 34, last sector 2047, and select ef02 as the partition code.

      gdisk command
        [root@centos ~]$ sudo gdisk /dev/vda
      GPT fdisk (gdisk) version 0.8.10

      Partition table scan:
      MBR: MBR only
      BSD: not present
      APM: not present
      GPT: not present


      ************************************************** *************
      Found invalid GPT and valid MBR; converting MBR to GPT format
      in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
      typing 'q' if you don't want to convert your MBR partitions
      to GPT format!
      ************************************************** *************

      # Enter 'n' (add a new partition)
      Command (? for help): n
      # Enter (default:2)
      Partition number (2-128, default 2):
      # Enter (default 34)
      First sector (34-2047, default = 34) or {+-}size{KMGTP}:
      # Enter (default 2047)
      Last sector (34-2047, default = 2047) or {+-}size{KMGTP}:
      # Enter 'ef02'
      Current type is 'Linux filesystem'
      Hex code or GUID (L to show codes, Enter = 8300): ef02
      Changed type of partition to 'BIOS boot partition'

      # Enter 'w' (write table to disk and exit)
      Command (? for help): w
      Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
      PARTITIONS!!

      # Enter 'y'
      Do you want to proceed? (Y/N):y
      OK; writing new GUID partition table (GPT) to /dev/vda.
      Warning: The kernel is still using the old partition table.
      The new table will be used at the next reboot.
      The operation has completed successfully.
  4. Install grub in the new boot partition.

    Install grub
    #Recognize new partition
    [root@centos ~]$ sudo partprobe
    #Install GRUB
    [root@centos ~]$ sudo grub2-install /dev/vda
    Installing for i386-pc platform.
    Installation finished. No error reported.
  5. Execute the reboot command to reflect the changes.

    Restart command
    [root@centos ~]$ sudo reboot
  6. Use the lsblk command to check whether the disk partition table format has been changed properly.

    Confirm format change
    [root@centos ~]$ sudo fdisk -l
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/vda: 3221.2 GB, 3221225472000 bytes, 6291456000 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: gpt
    Disk identifier: D9C42684-E18C-4B8F-9388-C2F2CDC093ED
    # Start End Size Type Name
    1 2048 6291455965 3T Linux filesyste Linux filesystem
    2 34 2047 1007K BIOS boot BIOS boot partition