I made a bootable USB flash drive with the Solus OS distribution. Since the startup path of
LiveOS/squashfs.img
has changed, the mount point has also changed. After loading the Live CD, os-installer stops because the path
/run/initramfs/live/LiveOS/squashfs.img
has been changed to
/run/initramfs/live/multiboot/Solus-4.1-Budgie/LiveOS/squashfs.img
As soon as I fixed the file
/usr/lib64/python2.7/site-packages/os_installer2/__init__.py
os-installer started working. In this regard, the question arises: how can I edit "rootfs.img" inside "squashfs.img" to fix the file "__init__.py"?

    alexanderzhirov You've clearly got a dodgy ISO if this is happening. The other option is you're booting off of the partition on the USB instead of the USB drive.

        5 days later

        Justin Yes, I originally wanted to do that. In general, I wanted to make the partitions of the flash drive (I have it at 64 GB). Then, in each section, make "dd" for each image I need, and then register them in GRUB so that when I boot, select the boot partition I need. The bottom line is that GRUB is not able to transfer the download to the ISO 9660 format file system via the "chainloader". Therefore, I had to abandon this idea and use booting from a disk images.

            alexanderzhirov Some ISOs support things like multiboot where you have several ISOs on a USB drive but I'm not sure if Solus does. There's a few tools like that out there one was called YUMI or similar if I recall.

                Justin Yes, I used it. But after recording, I fixed the config manually and my image started to load. But there was a problem with the installation due to a change in the mount point that I edited.