Building the Docker image

[the-JJ]

Hello,
I managed to get BrowserBox running via Docker with the shipped image (ghcr.io/browserbox/browserbox:latest@da07fd90fa9d).

However, when I try to build the image myself (to attempt development) using docker build in the root of the project (using the provided Dockerfile), once I access https://localhost:8080, I get some combination of HTTP Connection Refused, PR_END_OF_FILE_ERROR, or connection reset errors.

It smells like a HTTPS issue, but I can't be sure. All other configuration remains the same (I tried running from both run_docker.sh and a custom docker compose file) - the official image works, the custom one doesn't.

I tried accessing from different browsers and with clearing cache, but without success.

There are no obvious errors in the docker output either, and this is the final pm2 status:

browserbox-1   | ┌────┬──────────────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
browserbox-1   | │ id │ name                     │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
browserbox-1   | ├────┼──────────────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
browserbox-1   | │ 1  │ basic-bb-main-service    │ default     │ 7.1.0   │ fork    │ 1055     │ 0s     │ 3    │ online    │ 0%       │ 2.8mb    │ bbpro    │ disabled │
browserbox-1   | │ 2  │ devtools-server          │ default     │ 1.0.0   │ fork    │ 787      │ 0s     │ 0    │ online    │ 0%       │ 2.8mb    │ bbpro    │ disabled │
browserbox-1   | │ 3  │ run-docspark             │ default     │ 2.5.8   │ fork    │ 1073     │ 0s     │ 0    │ online    │ 0%       │ 2.8mb    │ bbpro    │ disabled │
browserbox-1   | │ 0  │ start_audio              │ default     │ 7.1.0   │ fork    │ 579      │ 0s     │ 0    │ online    │ 0%       │ 2.8mb    │ bbpro    │ disabled │
browserbox-1   | └────┴──────────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

Any tips on how to build my own docker image out of this would be appreciated.

[o0101]

Hey @the-JJ sorry about missing your discussion point! I did not see it until today.

Building the docker image is easy, if you know how! 😂 You can't just use docker build, there's a few special steps that need to be taken.

So, we have a script for that. It's called: ./deploy-scripts/build_docker.sh

We run the build on macOS. If you're building on other platforms you may have issues with the issue not being transferrable.

Also, to run the image, it's also not hard, if you know how! 😆 You can't just use docker run you need to again use a special script to take care of the special things it takes to run BrowserBox on Docker!

We have a name for that one, too. It's called: ./deploy-scripts/run_docker <PORT> <HOSTNAME> <EMAIL>

HOSTNAME needs to be either localhost or the FQDN that resolves to your instance via DNS.