2022-02-25 14:40:34
For the Linux system, you can use the image self-check tool provided by JD Cloud. Before exporting an image from the external environment, run the self-check tool to check key system configurations and make adjustments based on the check report.
In order to ensure the availability and ease of use of the imported image as much as possible, during the image importing process, the system will detect the key configuration in the image. if it does not meet the requirements, the import will fail. Therefore, it is recommended that you confirm the system configuration by referring to the basic image requirements in the Private Image Import, and use the image self-check tool to check the main configuration before importing images.
The operating systems determined to be supported include: CentOS, Ubuntu, Debian, SLES (SUSE Linux Enterprise Server), OpenSUSE, RedHat and other Linux released versions.
chmod +x jcs-image-tool sudo ./jcs-image-tool
Detection item | Inspection requirements | Consequences of non-compliance | Recommended actions |
---|---|---|---|
jcloudAgent | Correctly install JCS-Agent | cannot write password, key, and custom data; cannot report instance machine monitoring data | Correctly install JCS-Agent. Please refer to Official Image System Components |
iNode | The inode usage rate is not greater than 98% | If other tasks occupy the system space after the instance is enabled, it may cause insufficient space | Reserve enough inode resources |
security | SELinux service is not enabled | The instance cannot be enabled normally | Do not enable SELinux by modifying /etc/selinux/config |
diskSizeCheck | the system disk cannot be larger than 500GB | the image cannot be imported | Create an image after adjusting the capacity of the system disk |
SSH | The SSH service is enabled | the instance cannot be connected remotely from the console, and cannot be remotely logged in via SSH | Enable the SSH service |
password | passwd command exists | cannot add new user password setting | Retain passwd command |
root | A root account exists | Cannot remotely connect or log in to the instance via SSH using the password or key when the instance was created | Retain the root account |
shadow | file permission root can be read and written | cannot write passwords, keys, and custom data | ensure that the root user has read-write permission |
diskUsage | the disk usage is not greater than 98% | if other tasks occupy system space after the instance is started, it may cause insufficient space | When creating an instance from an imported image, set a large enough disk capacity to ensure normal service operation. |
qemu-guest-agent | qemu-guest-agent is not installed | may cause important system component JCS-Agent fail to run normally | Uninstall qemu-guest-agent |
lvm | Not use LVM | Unable to enable the instance normally | Not use LVM |
partition | Use MBR partition | Unable to enable the instance normally | Use MBR partition |
diskCharacterCheck | Configure fstab correctly | Unable to enable the instance normally | Use /dev/vda or uuid form to configure automount |
network | NetworkManager is not enabled | Network may be unavailable due to conflict with network services | Disable or delete NetworkManager |
firewall | the iptables service has been disabled | the access policy configured in the JD cloud environment is invalid, which may cause some internal services to fail to operate normally due to restricted access | Disable the firewall |
driver | the virtio driver has been compiled into the kernel or into a kernel module | the instance cannot be enabled normally | Install virtio driver |
我们的产品专家为您找到最合适的产品/解决⽅案
1v1线上咨询获取售前专业咨询
专业产品顾问,随时随地沟通