Open Gedanke opened 1 month ago
@rafaelsideguide any ideas why this is happening?
Hey @Gedanke ! I just reviewed our docker implementation and wasn't able to reproduce this error; I was able to run both scrape and crawl with no problems. This might not be relevant, but which system are you using? Could you please try updating your Docker and rebuild the containers without cache?
@Gedanke Are you using a proxy? I am also using a proxy and have the same issue.
@Gedanke Are you using a proxy? I am also using a proxy and have the same issue.
Hey @Gedanke ! I just reviewed our docker implementation and wasn't able to reproduce this error; I was able to run both scrape and crawl with no problems. This might not be relevant, but which system are you using? Could you please try updating your Docker and rebuild the containers without cache?
Thank you very much! This case is running on my computer wsl2 system. Yesterday I used source code to build firecrawl, which can provide normal service. But these days, I can't launch it from docker. My computer has been using the agent, and I was still able to build docker normally around the beginning of July.
@Gedanke Are you using a proxy? I am also using a proxy and have the same issue.
Sure, my computer has been using the agent, about the beginning of July, I can still build docker normally. But recently I couldn't launch it from docker. The same problem can occur on another server that does not use a proxy.
@dgedanke @cypher256 are you still facing this issue? Added stale tag as we didn't receive any comment on this issue for more than 40 days.
@dgedanke @cypher256 are you still facing this issue? Added stale tag as we didn't receive any comment on this issue for more than 40 days.
I'm sorry for taking so long to reply. I may have found the problem last month. My equipment environment does not visit https://registry.npmjs.org. To do this, I set up a mirror to NPM https://registry.npmmirror.com.
RUN corepack enable
this order will make pnpm access the official https://registry.npmmirror.com, not my default https://registry.npmjs.org.
Even if I add RUN NPM config set registry https://registry.npmmirror.com
at the end, or to write https://registry.npmmirror.com
into the configuration file, the new image is still will not take effect.
I ended up solving the problem that way.
# RUN corepack enable
# use npm to install pnpm, skip corepack
RUN npm config set registry https://registry.npmmirror.com
RUN npm install -g pnpm && \
pnpm config set registry https://registry.npmmirror.com
And,
$ curl http://127.0.0.1:3002/test
Hello, world!
But it's not a good choice. Shutting down corepack and losing npm package management could be potentially risky.
Describe the Bug
I tried to start Firecrawl from docker.
Worker-1 and api-1 didn't work. I can build it, but I can't run it.
https://registry.npmjs.org/pnpm/latest is accessible.
So, what causes this phenomenon?