Long-Term Supported Versions

    Innovation Versions

      User Guide

      Start a Kuasar sandbox.

      1. Ensure that Kuasar and related components have been correctly installed and configured.

      2. Prepare the service container image. Assume that the container image is busybox. Use the iSula container engine to download the container image.

        isula pull busybox
        
      3. Prepare the YAML files for the pod and container. The file examples are as follows:

        $ cat podsandbox.yaml 
        metadata:
          name: busybox-sandbox
          namespace: default
          uid: hdishd83djaidwnduwk28bcsc
        log_directory: /tmp
        linux:
          namespaces:
            options: {}
        
        $ cat pod-container.yaml
        metadata:
          name: busybox
        image:
          image: docker.io/library/busybox:latest
        command:
        - top
        log_path: busybox.log
        
      4. Start a pod.

        $ crictl runp --runtime=vmm podsandbox.yaml
        5cbcf744949d8500e7159d6bd1e3894211f475549c0be15d9c60d3c502c7ede3
        

        Check the pod list. The pod is in the Ready state.

        $ crictl pods
        POD ID              CREATED              STATE               NAME                NAMESPACE           ATTEMPT
        5cbcf744949d8       About a minute ago   Ready               busybox-sandbox    default             1
        
      5. Create a service container in the pod.

        $ crictl create 5cbcf744949d8500e7159d6bd1e3894211f475549c0be15d9c60d3c502c7ede3 pod-container.yaml podsandbox.yaml
        c11df540f913e57d1e28372334c028fd6550a2ba73208a3991fbcdb421804a50
        

        View the container list. The container is in the Created state.

        $ crictl ps -a
        CONTAINER           IMAGE                              CREATED             STATE               NAME                ATTEMPT             POD ID
        c11df540f913e       docker.io/library/busybox:latest   15 seconds ago         Created             busybox            0                   5cbcf744949d
        
      6. Start the service container.

        crictl start c11df540f913e57d1e28372334c028fd6550a2ba73208a3991fbcdb421804a50
        

        Check the container list. The container is in the Running state.

        $ crictl ps
        CONTAINER           IMAGE                              CREATED             STATE               NAME                ATTEMPT             POD ID
        c11df540f913e       docker.io/library/busybox:latest   2 minutes ago       Running             busybox            0                   5cbcf744949d8
        

        NOTE: You can also run a crictl run command to start a pod with a service container.

        $ crictl run -r vmm --no-pull container-config.yaml podsandbox-config.yaml
        
      7. Stop and delete the container and the pod.

        crictl rm -f c11df540f913e
        crictl rmp -f 5cbcf744949d8
        

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份