Puppy Package Manager is telling you that luakit is missing the default-dbus-session-bus lua5.1-filesystem. I first searched pkgs.org as it provides a consolidate search platform for most major distros. That lead me here, https://ubuntu.pkgs.org/18.04/ubuntu-un ... 4.deb.html. Usually there will be a link to download a package. [Had there been one it is likely Puppy Package Manager would have known about it and could download it]. But there was none. So I followed the url to the home page, https://lunarmodules.github.io/luafilesystem/ which advises:
LuaFileSystem can be installed using LuaRocks:
$ luarocks install luafilesystem
LuaRock is available via Puppy Package Manager.
Before you get deep into the weeds, let me urge you to reconsider you decision to run as a 'Full Install". Puppys are designed to run as Frugal. The 'technique' to run as 'Full' was developed 15 years ago when most computers were single processor and sold with less than 512 Mbs of RAM. It enabled the booting time to be reduced by a couple of seconds. It has not been worked on since. It exposes your system to all the malware since developed. [Puppys first line of defense is that it boots from READ-ONLY (uncorruptible) file-systems as a 'Frugal']. The first and every time you install or delete something into a 'Full Install" which breaks it, you'll have to 'start from scratch'. They are almost impossible to repair.
2Gbs should suffice for bionicpup64 under most circumstances. Adding the boot argument "no copy" will enable it to use the least amount of RAM for holding system files. But your most likely problem is web-browsers. How are you running them? Adding a swapfile can also help during web work. [Open a terminal and type 'pupswap' without the quotes]. But I suggest you switch to any of those offered as portables, https://www.forum.puppylinux.com/viewforum.php?f=90. Websites without your permission download files to cache on your computer so that when you view a web-page again they don't have to download it again. Unless you are using a portable or have manually employed a technique to have cache stored elsewhere, it gets stored in RAM. Graphic-rich websites can quickly consume 100s of Mbs of your RAM. Portable Web-browsers automatically locate the storing of web-cache in their own folders, which most people just place on their hard-drive: ala Windows portables.
You are even better off running Xenialpup64 than running Bionicpup64 as a 'Full'. Xenialpup64 is still able to do what Bionicpup64 can, but uses lighter weight applications. Only when Xenialpup64's glibc libraries become too old to support modern web-browsers would there be a problem. Tahrpup64, first published in 2015, only incurred that problem this year.
