Visualise a container as using the same base sfs, but having its own save area. When you install something in the main session then that's stored in the main sessions save area, which isn't visible by containers (that only see the base sfs + the containers own save area). If after installing into the main session you remastered a new base sfs, then containers would see the additional programs.belham2 wrote:I un-installed the chromium from Easy 0.9.6 PPM, restarted, then installed your chromium.pet and the apulse. Every thing works good. Still cannot get Chromium to work in a Container (for some reason, 'Easy Container Management' won't recognize chromium is installed, so that one could make a container for it and run it in that.
It's no biggie, though, I am using rufwoof's trick he mentioned, and I run the "Container Desk", then download your apulse.pet & chromium.pet, install them, and chromium runs great (with sound) while inside the 'Container Desk'. Hopefully that'll afford some protection if I come across something bad while browsing, since it'll be operating inside the container-desk.
A problem is how can you install additional things into a container. That's easy in the desk container as its a full desktop setup, so you can run petget/PPM etc. inside that, but for other containers you'd have to manually copy files across.
Running chrome with --no-sandbox does remove much of Chrome's own internal security, but being in a container somewhat reinstates that security. Running a container as non-root should enable chrome to work as intended so you'd have both the internal chrome security and security of running inside a container. Barry however dropped being able to setup a container to run under a non-root userid, so AFAIK that isn't a current option.