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 kata-runtime 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
  5. Open the /etc/isulad/daemon.json file. If kata-runtime is not configured, set runtime to kata-runtime.

    "runtimes": {                                                                               
        "kata-runtime": {                                                                   
            "path": "/usr/bin/kata-runtime",                                                 
            "runtimeArgs": [                                                                

Interconnection Guide

This section describes how to interconnect StratoVirt with kata-runtime in the iSula security container.

  1. Create the script in any directory (for example, /home) and add the execute permission to the file as the root user.

    # touch /home/
    # chmod +x /home/

    The content of is as follows, which is used to specify the path of StratoVirt:

    export STRATOVIRT_LOG_LEVEL=info  # set log level which includes trace, debug, info, warn and error.
    /usr/bin/stratovirt $@
  2. Modify the kata configuration file (default path: /usr/share/defaults/kata-containers/configuration.toml). Set the Hypervisor type of the security container to stratovirt, kernel to the absolute path of the kernel image of StratoVirt, 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 configuration reference is as follows:

    path = "/home/"
    kernel = "/var/lib/kata/vmlinux.bin"
    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
  3. Use the root permission and isula command to run the BusyBox security container and interconnect StratoVirt with it.

    # isula run -tid --runtime=kata-runtime --net=none --name test busybox:latest sh
  4. 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

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.