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.
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.