docker-firefox VS distrobuilder

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.

LXC

which is what docker/podman/containerd use. If you want full system emulation look into LXC/LXD.

LXD is a manager for Linux Containers (LXC), which lets me spin up a kind-of lightweight VM for any distro, instantly. I use it to run proprietary software isolated from the rest of my system (such as Steam); disposable environments for trying stuff out, and running software that doesn't jive well with Nixos.

Check this thread on linuxcontainers LXD forum. Half way down Simos points to the eventual solution:

I found this website https://linuxcontainers.org/ and I am going to test that out for server just to see how it works.

Up to now the best documentation I have come across is the official one at linuxcontainers.org.

Containers, like LXC or Docker.

After five years managing physical servers, then another four years working with VM clusters, the value of Linux Containers(LXC) and their eventual productization as Docker appealed to me.

Docker introduced container images to the technology world, making container images a standardized delivery unit. In fact, before Docker, containerization technology already existed. Let's talk about a more recent technology, LXC (Linux Containers) in 2008. Compared to Docker, LXC is less popular since Docker provides container images, which can be more standardized and more convenient to migrate. Also, Docker created the DockerHub public service, which has become the world's largest container image repository. In addition, containerization technology can also achieve a certain degree of resource isolation, including not only CPU, memory, and other resources isolation, but also network stack isolation, which makes it easier to deploy multiple copies of applications on the same machine.