Puppy Linux Discussion Forum

Works great! See blog post:

https://bkhome.org/news/202105/run-slac ... asyos.html

Thinking I might convert a few more of the pups, to run in EasyOS.

Interesting thought: you could have 3 or 4 pups running simultaneously in containers, and flip between any of them. Don't know why I would want to do that, just an interesting thought.

I fixed some container-related issues in EasyOS, so probably best to upgrade to Easy 2.7.3 before installing Slacko.

I expect to be uploading 2.7.3 several hours from now.

If you install Slacko and it runs fine in container, then good.

However, after upgrading to 2.7.3, with Slacko not running as a container, go to /mnt/wkg/containers/slacko/.session/.control and delete file 'ec-run'.

Then when start the container, by clicking on "slacko" on the desktop, 'ec-run' will get recreated. It has some improvements.

Easy 2.7.3 has been released:

https://bkhome.org/news/202105/easyos-v ... eased.html

And forum feedback thread:

viewtopic.php?f=63&t=2850

BarryK wrote: ↑Tue May 04, 2021 9:34 am

...Interesting thought: you could have 3 or 4 pups running simultaneously in containers, and flip between any of them. Don't know why I would want to do that, just an interesting thought.

In today's environment isolating applications is AFAIK the only way to maintain security and privacy. Other than web-browsers, the weakest link among applications is Wine. WineHQ still advise that its developers make no effort to secure it; leaving that up to the developers of the OSes under which Wine is to be run. Wine doesn't appear to be an application which can, itself, be containerized: it requires an operating system. That was my primary interest in running containerized racy under EasyOS-buster.

But there may be two another ways (untested). The main reason to run Wine is to make use of many of the thousands of programs which were developed under Windows 32-bit. To run such Wine under Xenialpup64 (itself) --or other 64bit Puppys-- requires loading the 32-bit compatibility SFS, then installing a 32-bit wine pet. Containerized OSes can't mount SFSes. But, SFSes can be converted to pets and installed.

The second method would be to make use of Wine AppImages. Again, these can't be used AS-IS by a containerized OS. But AppImages can be extracted (by, for example, UExtract) and many of them including the wine-staging.appimage, https://github.com/mmtrt/Wine_Appimage/releases when extracted are 'rox-apps'. It should be possible to located them in the containerized OSes /opt folder with appropriate binary-symlinks in the containerized OSes /usr/bin, and desktop files and pixmaps to provide menu entries.

Lastly, although containerized web-browsers, themselves, provide a high level of security, a web-browser run from a containerized OS may provide an even higher level of deterrence against finger-printing by websites or hackers.

BarryK wrote: ↑Tue May 04, 2021 9:34 am

Interesting thought: you could have 3 or 4 pups running simultaneously in containers, and flip between any of them. Don't know why I would want to do that, just an interesting thought.

Actually, there is one reason: each Pup distro has it's own package manager and package repository. So if there is an app in the Ubuntu repository, then can install it from, one of the Ubuntu-Pups running in a container. Or, if there is a needed package from the Slackware repository, run Slacko in a container.

Note though, not all apps will run, due to being in a restricted container environment. Though, it is possible to ease the security restrictions for any container.

BarryK wrote: ↑Wed May 05, 2021 12:46 am

Actually, there is one reason: each Pup distro has it's own package manager and package repository. So if there is an app in the Ubuntu repository, then can install it from, one of the Ubuntu-Pups running in a container. Or, if there is a needed package from the Slackware repository, run Slacko in a container.

Pretty nice feature, being able to run a distro inside a container. Having access to the debian repos is sometime needed. Often though, the application one wishes to use are debs from github projects or other sources.
for example....
https://github.com/markmal/freeship-plu ... tag/5.0.36
https://www.virtualbow.org/download/
https://opencpn.org/OpenCPN/info/downloadopencpn.html

My own experience installing some of these programs is when the debian capable distro uses apt instead of PPM as it's package manager. Is there a way to run a dog or some other flavor that is built around apt as its default package manager?

williwaw wrote: ↑Wed May 05, 2021 4:27 am

BarryK wrote: ↑Wed May 05, 2021 12:46 am

Actually, there is one reason: each Pup distro has it's own package manager and package repository. So if there is an app in the Ubuntu repository, then can install it from, one of the Ubuntu-Pups running in a container. Or, if there is a needed package from the Slackware repository, run Slacko in a container.

Pretty nice feature, being able to run a distro inside a container. Having access to the debian repos is sometime needed. Often though, the application one wishes to use are debs from github projects or other sources.
for example....
https://github.com/markmal/freeship-plu ... tag/5.0.36
https://www.virtualbow.org/download/
https://opencpn.org/OpenCPN/info/downloadopencpn.html

My own experience installing some of these programs is when the debian capable distro uses apt instead of PPM as it's package manager. Is there a way to run a dog or some other flavor that is built around apt as its default package manager?

You don't need the PPM to install a DEB. Just download the DEB and click on it. That should work for all the pups, well, it used to.

In EasyOS, if you download a DEB and right-click on it, there are menu choices to either open it up or install it. The former runs Xarchive, the latter runs 'petget'.

After installing, it will be listed as installed in the PPM window.

The problem with installing applications not available via PPM isn't that EasyOS can't manage the packages but the absence of dependency checking. One could examine the appropriate webpage in the source distro or pkgs.org. But another possibility --not tested by me-- might be to install sc0ttman's pkg-cli (not really a cli as it also has GUIs), https://oldforum.puppylinux.com/viewtop ... 0a#p985531. Peebee, and rockedge have reported great success employing it in Puppies. And IIRC wiak and rockedge reported success employing it in Weedog.

BarryK wrote: ↑Wed May 05, 2021 11:29 am

You don't need the PPM to install a DEB. Just download the DEB and click on it. That should work for all the pups, well, it used to.

In EasyOS, if you download a DEB and right-click on it, there are menu choices to either open it up or install it. The former runs Xarchive, the latter runs 'petget'.

After installing, it will be listed as installed in the PPM window.

right click works well if there are not too many dependincies to chase down, otherwise letting the package manager do its thing is easier. more complex are the .debs supplied in ubuntu flavored ppa's, often not available without a way to get to the signed repo.

did manage to get the three apps in question installed using fossa in a container :)

I have never been able to install this machine on my laptop. Thank you Easyos ... it works in container! Irony!