After updating to version 2026.02.2 and higher, the platform does not work

Problem

After updating the platform to version 2026.02.2 or higher, the platform stopped working.

Cause

Starting with version 2026.02.2, the platform architecture includes a new container, vm_back. As a result, configuration templates for some services have been moved from the vm_box container to the new vm_back container. For example, the ip-fabric configuration template. The issue occurs due to custom patches (YAML files) that still reference the vm_box container. For more information about patches, see Container modification via patches.

Diagnosis

To confirm the cause of the issue:

1. Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
2. Check for custom patches:
   
   1. Open the platform configuration file:
      

      cat /opt/ispsystem/vm/config.json

   2. Examine the Patches section. This section lists all patches, including custom ones:

      Example output

      "Patches":{"channelp":{"base64_compose":"c2VydmljZXM6CiAgdm1fYm94OgogICAgZVfVElNRU9VVDogMC4zCg=="}

      Examples of system patch names:

      • for the “Integration with DNSmanager 6” module — vmdnsmgr;
      • for the “Integration with IPmanager 6” module — vmipmgr.
3. Check the contents of the custom patch:
   
   1. Open the patch file.
   2. Inspect the Services section. An indicator of the issue is when the services section references the vm_box container.
      
      Example of the services section with vm_box

      services:
        vm_box:

4. Verify the patch functionality. For example, the issue is confirmed if you observe the following:

   • the patch edits a file in the vm_box container, but this file no longer exists in the container;
   • the patch copies a file to the vm_box container, but the file is no longer being copied.

Solution

To resolve the issue, replace the vm_box container with vm_back in the custom patch:

1. Connect to the server with the platform via SSH. For more information about connecting via SSH, see Workstation setup.
2. Disable the target patch:
   

   vm remove-patch -p=<patch_name>

   Comment:

   • <patch_name> — the unique name of the patch.
3. Edit the patch file: replace vm_box with vm_back.
   
   Example patch after changes

   version: "3.5"
   services:
     vm_back:
       command:
         - bash
         - -c

4. Apply the new patch:
   

   vm add-patch -p=<patch_name> -f=</path/to/patch.yaml>

   Comment:

   • <patch_name> — the unique name of the patch;
   • </path/to/patch.yaml> — the path to the file containing the patch contents.
5. If multiple custom patches exist, repeat these steps for each patch.
6. Verify that the platform is functioning correctly.