Container Issue After Installing iSulad

[MattXLei]

Describe the bug
After installing iSulad with openEuler using AWS, I tried running a few basic commands dealing with containers. I initially wasn't sure what container image registry address to configure (if I used Docker, it'd be "docker.io", but since I used AWS for openEuler, would it be "amazonaws.com"?), so that may be the reason behind this issue. Anyways, I was able to start iSulad and could list all containers in my environment, but when trying to create a container, it didn't work, so I downloaded busybox, but I still got an error after trying to create a container again.

To Reproduce
Steps to reproduce the behavior:

1. Follow the instructions on the AWS Marketplace link to launch an instance (I chose "openEuler-22.03-LTS-SP2 (arm64)" from the AWS Marketplace AMIs). I downloaded the key-value pair as a .pem file and named it like so:

2. After launching the instance, connect to the instance typing this on a Linux terminal in the same directory as your key-value pem file: ssh -i "openEuler-try.pem" openeuler@ec2-... (rest of the DNS)".

3. After connecting to the instance, type "sudo yum install -y iSulad" and wait for iSulad to install (first image below). Start iSulad with "sudo systemctl restart isulad" or "sudo isulad" (only the former works for some reason, as in the second image below). You can also install busybox if you don't have it/can't create a container on the first try, though I'm not sure that'll do anything (third image below):

----- -----

4. See one of these errors upon running "sudo isula create -t -n test busybox"

-----

Expected behavior
You cannot create a new container

Screenshots
Shown above.

Desktop (please complete the following information):

• OS: macOS arm64
• Browser: Chrome
• Version: Latest