sfsget Not Recognizing Locally Created SFS

[myke]

Remembering that I am using a VM environment with vda1 and vda2 as EasyOS Scarthgap 6.5 guest, I created an sfs file with the associated specs and png files and sfsget does not recognize them. The three files mentioned previously are in /mnt/wkg/sfs/puppy/slackware/15.0/ and include Slacko_15_i386.sfs , Slacko_15_i386.specs and Slacko.png and are from a downloaded S15Pup32-22.12-24.12.01.iso. I admit I forgot to include the revision number of the iso in the title of the created sfs. Is that the reason that sfsget fails to recognize it?

[Caramel]

To install a local SFS you need to be offline. (See viewtopic.php?p=77097#p77097)

(You can go offline by clicking on the network tray icon and choose "Disconnect".)

[myke]

Right now, I have successfully created two containers, each with an OS as sfs. but neither of them will display. When I click on an icon, it causes the screen to flip to display the OS but instead of displaying, it flips back to the main screen. I followed the instructions in "How to run a Linux distribution in a container" version dated May 4, 2021 and both OSes are i686 Puppy Linuxes, one based on Ubuntu Noble, (Noblepup32) the other on Slackware 15.0 (S15Pup32). I used folder names Noblepup_24.04-241201_i686 and Slacko_15-22.12-241201_i686, respectively.

[Caramel]

I tested with NoblePup32 (https://sourceforge.net/projects/pb-gh- ... 2_release/) and the page How to run a Linux distribution in a container

In the window "Container secxurity", it is important to choose Xephyr in X Server.

The desktop is displayed (after a very long black screen)

There is no button to flip back in the main system nor message with Alt+F6

Screenshot.png (36.85 KiB) Viewed 497 times

NB : The web browser in the container do not work because it is located in adrv_upupnn+bw_24.sfs and the container was made with only the main sfs.
However we can add the files from adrv_upupnn+bw_24.sfs in the folder Noblepup_24.04-241201_i686 before executing dir2sfs (I didn't tested)

[myke]

In my case, I checked. Both pup sfs's have Xepher selected, not Xorg. I thought it might be that the vda2 space was low. So, I resized the img in the host and vda2 in the guest. Then I tried again: in each case, it flips to go to the container and instantly flips back - with no wait.
In short, the questions that come to mind are: is it the EasyOS in a global VM, the 32-bit architecture, using a Puppy as source or a mistake in the procedure that I have overlooked? I am going to try working with an amd64 architecture to see whether the problem is the i686 architecture. I also have some old sfs that are 32 bit in an old EasyOS set-up originally on a USB thumb drive. I will also try an old Buster img that I will use google drive to do the transfer to the EasyOS guest. At some point, I would like to move vda1 and vda2 to an actual partition on the host OS as sda3 and sda4 and try dual-booting and eventually get rid of Linux Mint. In any case, I am uploading the specs files for the two cases.

[Caramel]

In your NoblePup specs, the size seems small

SFS_DB_size='352828'

In my test :

SFS_DB_size='1002624'

PS : I had made an error in creating the sfs as i had left easy as a dependancy. I will retry

Edit : apart from a faster first start, no visible difference