Long-Term Supported Versions

    Innovation Versions

      Interconnecting with iSula Security Containers


      To provide a better isolation environment for containers and improve system security, you can interconnect StratoVirt with iSula security containers.

      Interconnecting with an iSula Security Container


      iSulad and kata-containers have been installed, and iSulad supports the containerd-kata-shim-v2 container runtime and devicemapper storage driver.

      The following describes how to install and configure iSulad and kata-containers.

      1. Configure the yum source and install iSulad and kata-containers as the root user.

        # yum install iSulad
        # yum install kata-containers
      2. Create and configure a storage device.

        You need to plan the disks, for example, /dev/sdxx, which will be formatted.

        # pvcreate /dev/sdxx
        # vgcreate isulaVG0 /dev/sdxx
        # lvcreate --wipesignatures y -n thinpool isulaVG0 -l 95%VG
        # lvcreate --wipesignatures y -n thinpoolmeta isulaVG0 -l 1%VG
        # lvconvert -y --zero n -c 512K --thinpool isulaVG0/thinpool --poolmetadata isulaVG0/thinpoolmeta

        Add the following information to the /etc/lvm/profile/isulaVG0-thinpool.profile configuration file:

        activation {

        Modify storage-driver and storage-opts in the /etc/isulad/daemon.json configuration file as follows. Set the default storage driver type overlay to devicemapper.

        "storage-driver": "devicemapper",
        "storage-opts": [
      3. Restart isulad.

        # systemctl daemon-reload
        # systemctl restart isulad
      4. Check whether the iSula storage driver is successfully configured.

        # isula info

        If the following information is displayed, the configuration is successful:

        Storage Driver: devicemapper

      Interconnection Guide

      This section describes how to interconnect StratoVirt with kata-containers to access the iSula container ecosystem.

      1. Modify the kata configuration file. Its default path is /usr/share/defaults/kata-containers/configuration.toml. You can also configure the file by referring to configuration-stratovirt.toml in the same directory. Set the Hypervisor type of the security container to stratovirt, kernel to the absolute path of the kernel image of kata-containers, and initrd to the initrd image file of kata-containers. (If you use yum to install kata-containers, the two image files are downloaded and stored in the /var/lib/kata/ directory by default. You can also use other images during the configuration.)

        The configurations are as follows:

        path = "/usr/bin/stratovirt"
        kernel = "/var/lib/kata/kernel"
        initrd = "/var/lib/kata/kata-containers-initrd.img"
        block_device_driver = "virtio-mmio"
        use_vsock = true
        enable_netmon = true
        sandbox_cgroup_with_emulator = false
        disable_new_netns = false
        disable_block_device_use = false
        disable_vhost_net = true
      2. Use the root permission and isula command to run the BusyBox security container and interconnect StratoVirt with it.

        # isula run -tid --runtime "io.containerd.kata.v2" --net=none --name test busybox:latest sh
      3. Run the isula ps command to check whether the security container test is running properly. Then run the following command to access the container:

        # isula exec –ti test sh
      4. Use a VM snapshot to accelerate startup of the security container and reduce the VM memory overhead.

        Modify the kata configuration file configuration.toml and set enable_template to true to allow the VM to start by creating a snapshot.

        # VM templating support. Once enabled, new VMs are created from template
        # using vm cloning. They will share the same initial kernel, initramfs and
        # agent memory by mapping it readonly. It helps speeding up new container
        # creation and saves a lot of memory if there are many kata containers running
        # on the same host.
        # When disabled, new VMs are created from scratch.
        # Note: Requires "initrd=" to be set ("image=" is not supported).
        # Default false
        enable_template = true

        After the enable_template configuration item is set to true, kata-containers checks whether a snapshot file exists in the default path (/run/vc/vm/template) during security container creation. If yes, kata-containers starts the VM using the snapshot file. If no, kata-containers creates a VM snapshot and start the VM using the snapshot file.

      5. Use the security component Ozone to further enhance the isolation of security containers.

        Modify the kata configuration file configuration.toml and set the configuration item ozone_path to the path of the Ozone executable file. (If StratoVirt is installed using yum, the Ozone executable file is stored in the /usr/bin directory by default.) After this item is configured, the Ozone security sandbox function is enabled to protect the VM against attacks after the virtualization layer isolation is broken and further enhance the isolation of StratoVirt security containers.

        # Path for the ozone specific to stratovirt
        # If the ozone path is set, stratovirt will be launched in
        # ozone secure environment. It is disabled by default.
        ozone_path = "/usr/bin/ozone"

      You can now run container commands in the test container.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.


      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.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

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


      ● 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
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份