docker-firefox VS neko

Here's a Firefox version. It won't be any better for quality/performance though. https://github.com/jlesage/docker-firefox

I use Apache for my primary web server accessed through 80/443, and I need to set up a reverse proxy to a Docker container. Specifically, I'm trying to set up a reverse proxy for this Firefox image so I can use it on the go.

There was a project on here a while back where you could basically host a Firefox instance on a VPS somewhere and use it over the web (reddit post about it). It was pretty cool. It was for use for things like private browsing anywhere you want. Something like that could push Orb into an area where it would be useful for folks with use-cases like that, and not just people with NAS/servers to manage.

I have setup Firefox docker that I can access from my nginx server. It's just normal https traffic so won't be blocked in a corporate environment. You might want to firewall it off from the rest of your network somehow and definitely add access controls to it. Works surprisingly well though

But let me clarify my question: let's say I'd like to run Firefox on docker and would need to be able to access it remotely. I could use a pre-built image like docker-firefox. But how can I verify that the Firefox that's included in this image has not been tampered with? Is there a way? If not, is there a (simpl-ish) way to download Firefox off mozilla.org and put it in a docker container together with a remote desktop server or a web server? Or would a simple Linux VM be the easier way?

The Firefox image (https://github.com/jlesage/docker-firefox/blob/master/Dockerfile) then installs Firefox, fonts and other tools.

I want to create docker image of Ungoogled Chromium, with a webUI for accessing the browser, similar to QNAP's Browser Station and this docker image of firefox.

I personally use neko-rooms with my friends for this purpose. Just let's all share a browser in a browser with plenty of options (Firefox, Chromium, Brave, etc.). You can also just use standard neko if you don't need multiple rooms.

Hey, you do you. It just sounds like an expensive way to avoid owning the hardware you want to debug to me.

Also, not to burst your bubble, but there are a few projects out there that do more-or-less what you're describing:

- https://store.steampowered.com/remoteplay/#together

- https://github.com/m1k1o/neko

If you're having fun, then continue by all means. I've just been nerd sniped by your cloud costs and I'm having flashbacks to seeing six-figure monthly AWS bills at startups that refused to buy their own GPU compute.

You could spin up something like Kasm Workspaces, Neko or Docker Webtop.

I ran into neko https://github.com/m1k1o/neko recently which has similar. It's more application centric than desktop centric, but both offer multi-player experiences & I just think that is the absolute coolest.