Closed openam closed 1 week ago
Is this from a fresh install or is this an existing one?
When I did npx @browserless.io/browserless create
it asked if it was ok to install @browserless.io/browserless@2.18.0. Is that what your asking about?
If not, a fresh install of what?
I was just curious if this is a project you've already had running for some time or not, but your response has the context I need. Thanks!
I have the same question, how to resolve it? @openam
Did you try to install browsers ? : npm run install:browsers
No, I didn't try doing that. I was trying to have it the docker image via the create
template. I did just look to see if that's an option in the scaffold/package.json, but it doesn't look like install:browsers
is an available script to run inside the Dockerfile.
There were a few bugs worked out yesterday that might have contributed to this, as well as I see that we do try and install browser dependencies with npx
after installing the required node_modules. There's a discrepancy where the wrong browser binaries are installed since npx
installs the latest stable package versus what's installed in the SDK application.
Going to get a fix for this here shortly.
Should now be fixed in 2.20.0!
@joelgriffith I'm still getting this error. I tried to docker rmi --force
all my old built images to try and force it not to use a cache. I also did a docker pull on the ghcr.io/browserless/chromium
image to get the latest. The error has more detail in it this time, but still says Couldn't load route "/chrome/content?(/)" due to missing browser binary for "ChromeCDP".
To be fair I'm doing this on SDK v2.20.2, since that's what existed when I tried it this morning.
I don't see where it does npx install of browser dependencies. I'm guessing it's part the step with npm run build
in it. Is that correct
Here is the docker file contents that ends up in ./build/Dockerfile. This docker file, and the output above indicate that it would have to be the npm run build
step that installs the browser.
I've followed Tuttles directions and got the exact same error.
History:
10013 nvm i 20
10014 npx @browserless.io/browserless create
10015 cd test-browserless-2-20-2
10018 nvm use 20
10019 npm run docker
10020 docker run -it --rm --platform=linux/arm64 -p3000:3000 my-browserless:arm
Exact same output error as his.
Describe the bug Using the SDK/cli to create a custom image with custom endpoints creates an image that appears to be missing pieces. i.e. ChromeCDP appears to be missing upon building the new image.
To Reproduce Steps to reproduce the behavior:
npx @browserless.io/browserless create
# it used @browserless.io/browserless@2.18.0in that new directory ran
npm run docker
docker run -it --rm --platform=linux/arm64 -p3000:3000 my-browserless:arm
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
n/a
Additional context Just to make sure that it should be working on my laptop I tried to run the regular image
docker run -it --rm --platform=linux/arm64 ghcr.io/browserless/chromium
it appears to start just fine. To be fair I haven't tried to connect to it. It does start up and doesn't throw an error.Is there something I'm missing? I'm not sure why it's looking for a ChromeCDP binary. I thought it was using the
ghcr.io/browserless/chromium
image. I also tried this specifyingghrc.io/browserless/chrome
but that I had to specify linux/amd64 because there wasn't an arm version available.