Replies: 4 comments 1 reply
-
Sort of found why it was breaking when launching from the extension: |
Beta Was this translation helpful? Give feedback.
-
This is interesting. I unfortunately don't know why Firefox requires Because fuse-overlayfs only works on Linux and has this problem with env vars, I will probably just add manual instructions to the repo wiki or extension. In the future, I might add an additional option to set up fuse-overlayfs instead of downloading runtime. Also, if you find why this problem happened or how to properly fix it, please let me know. |
Beta Was this translation helpful? Give feedback.
-
As I'm not really experienced in |
Beta Was this translation helpful? Give feedback.
-
I added instructions for using FUSE OverlayFS for the runtime. With the provided systemd user service, the runtime will be automatically linked when the user logs in, without the need to additional configuration or root access. See #214 for more details. |
Beta Was this translation helpful? Give feedback.
-
Hey,
For starters, thanks heaps for this project!
I've been stuffing around with trying to use overlayfs to use my system's firefox runtime instead of having FirefoxPWA download a new one for me. This nearly works perfectly ;)
Launching from CLI actually works fine:
This works great - runtime.patch works fine and I can see all the modifications in the /upper directory, and the PWA works fine!
The one issue I have yet to figure out is that launching from the browser doesn't work. The subprocess
firefox
does seem to start with the correct arguments, but it doesn't show any window. Maybe there are env vars that are persisting from the parent process? I'll look more into this, I can't imagine this is insurmountable given cli launch works fine.Just sharing in case it sparks interest! This is on Ubuntu 21.10 for reference, but I think fuse-overlayfs has worked ok for a while now.
Beta Was this translation helpful? Give feedback.
All reactions