Chrome running in container as user spot

I posted about support for running an app in a container as user "spot"; first-up was Firefox:

https://bkhome.org/news/202209/firefox-running-in-container-as-user-spot.html

I have now rebuilt the Chrome SFS, to also run as spot in a container. This is file 'chrome_105.0.5195.102-1_amd64.sfs', where the "-1" is the revision number. You can download via the "sfs" icon.

Upgrading of SFS files is not really properly implemented. If you already have Chrome SFS installed, and running in a container, go to the menu "Filesystem -> Easy Containers" and there is a choice to delete the Chrome container. Then, click on "sfs" to install the new one.

When Chrome is running, if you go to /mnt/wkg/containers/chrome/container/tmp, there is file 'chrome-xerrs.log', where you can see whatever Chrome is complaining about.

One complaint is it reports /dev/dri/card0 is missing. Yes, this is something I will investigate. A lot of apps want access to openGL. OK, that can be next on the to-do list.    

Tags: easy