I’ve been using the Firefox docker container through the gluetun docker container (runs great with proton and mullvad) and it’s been really great.
To me it’s kind of like a less restricted tor browser, for when you need something stronger in terms of speed or IP blocking. And maybe something more persistent.
And it always stays open even when you close your connection.
Some of my use cases are:
-
Anonymously downloading larger files through the clearnet.
-
Anonymous ChatGPT usage.
-
Manually looking for torrent magnet links (though I usually do that with the tor browser)
-
Accessing shadow libraries
Most of these containers don’t require any thing attached to the host - it can work headless. They are docker (just normal Linux inside) containers which are running processes such as Firefox and usually run something like KasmVNC giving fast, responsive (if using high bandwidth settings) remote desktop into the containers which runs the Firefox browser on a lightweight virtual desktop with a virtual display. I’d recommend looking into the concept from linuxserver.io’s Webtop container to understand the concept (and how cool they are!) In your case with obsidian they pretty much run a container and pass a bind mount for a Vault. This isn’t synced by default with anything but you could use Syncthing on the host to sync your vault from other devices or use Obsidian Sync.
Thanks for the reply. I’ve tried both Firefox and Obsidian containers from Linuxserver.io before, but when connecting I found there was no output. It made me wonder what was missing (like X11 or Wayland installed on the host) for an output to be generated.
My server is not headless (I installed GNOME) but runs without a screen connected. and the Firefox container does run kasmvnc.