Problems with Easy Containers

[Caramel]

I create this topic because the containers developed for Easy (Easy Containers) don't get the attention they deserve.

I will collect some tests or observations.

-The container xenialpup don't start.

A possible cause is the shared folder error visible in the expert security tab of easy container

capture18736.png (93.75 KiB) Viewed 841 times

It is written /mnt/wkg/home/shared instead of of /files/shared
(Note that for fossapup it's /home/shared and fossapup starts)

-appi and flappi are in the list of apps offered to run in a container. They probably not work (not tested)

-To download a sfs, Easy uses download_file (in /usr/sbin) that displays a window impossible to resize, to minimize or to move.

Moreover the window displays on the 2 workspaces (virtual desktops).
It's uncomfortable then the time of download is long.

[BarryK]

Yes, you're right the conatiners are getting neglected.
Some of those SFSs were created a long time ago, and need to be fixed.
I have written down the issues that you have reported into my to-do list.

[Caramel]

Test of the creation of a container (see https://easyos.org/dev/how-to-run-a-lin ... ainer.html) with VoidPup64-22.02-230505.iso (viewtopic.php?t=5270)

First extraction of puppy_vpup64_22.sfs from the iso
I'm extracted too adrv_vpup64_22.sfs (to have a browser in the container)
All the files from the sfs were copied in a folder "voidpup_22.02-230513_amd64"
Addition of a icon in the subfolder usr/share/pixmaps

voidpup.png (3.16 KiB) Viewed 743 times

Running of the dir2sfs script

Code: Select all

dir2sfs voidpup_22.02-230513_amd64

Edit : choose desk as install mode

In "SFS package database-entry creator" window :
Compiled in Linux distro : void
Distro release : rolling
Repository path : puppy/void/rolling

The 3 files voidpup_22.02-230513_amd64.sfs,voidpup_22.02-230513_amd64.specs and void.png have been created.

I'm copied the 3 files in /mnt/wkg/sfs/puppy/void/rolling, launched sfsget, selected puppy/void/rolling, installed voidpup.

And the container voidpup starts!

Screenshot(2).png (32.05 KiB) Viewed 743 times

NB : this screenshot has been taken after some play with the container. the message with "Press ALT-F6 to flip" in the middle of the screen has disappeared.

[Caramel]

Creation of a container depending of the container voidpup.

Just after the first launch of voidpup (or after a return at its initial state) You take a snapshot (with Easy Version Control in the menu section Files).It's a sfs file (named with rw,the date and hour of creation, for example : rw-202305161144.sfs)

Then you can install an application.
In my test it was okular :

Code: Select all

vpm i okular 

(vpm is the package manager of voidpup that replaces ppm)

No icon and no entry menu visibles. Test in terminal.

Okular don't want to launch because libmpeg13.so is missing.

Code: Select all

vpm i libmpeg123

Now it starts. Just test with a pdf file. Works

Take of a new snapshot.

Exit and closure of the container voidpup.

Opening of the snapshots by clicking on them.

Content copy of the second snapshot in a new folder (In my test okular_23.04.0-1_amd64 +, 23.04.0-1 is the version number of the installed okular)

Maybe optionnal, you remove of the folder the content of the first snapshot to reduce the size (Here it was 17MB less)

Verify there are a .desktop (in the subfolder usr/share/applications) and a .png (icon size 48x48pixels) (in the subfolder usr/share/pixmaps)
(In my test I've copied the okular.desktop and okular.png installed by the flatpak in another EasyOS)

And now, you can use dir2sfs with the folder

Code: Select all

dir2sfs okular_23.04.0-1_amd64

Let the individual install mode

In "SFS package database-entry creator" window :
Write voidpup in the dependancies form field.
Compiled in Linux distro : void
Distro release : rolling
Repository path : puppy/void/rolling
The Container and Menu sections are more tricky if there are several .desktop and icon images
(In the okular example , just let okluar.desktop , okular.png and Document;viewer)

All that's left is to copy the 3 files .sfs .specs .png produced by dir2sfs in /mnt/wkg/sfs/puppy/void/rolling.

Rest assured, it's much less painful to make a container that writing or reading this text.

[Caramel]

A tpoic on the containesrs already existed :
viewtopic.php?t=8222

[Caramel]

(EasyOS 5.4.1)

Small bug :

When we close the container fossapup window, the process dhcpcd created by the container is always active

# ps | grep fossapup
21505 root 0:00 dhcpcd: fossapup1 [ip4] [ip6]
23777 root 0:00 grep fossapup

and fossapup.sfs is always "mounted" to /mnt/wkg/containers/fossapup/.fossapup

[libertas]

Creation of a container depending of the container voidpup.

Just after the first launch of voidpup (or after a return at its initial state) You take a snapshot (with Easy Version Control in the menu section Files).It's a sfs file (named with rw,the date and hour of creation, for example : rw-202305161144.sfs)

...

Rest assured, it's much less painful to make a container that writing or reading this text.

If you could make a video showing how to do this it would be great!