Request timeout in docker

[Ardear]

Which package is this bug report for? If unsure which one to select, leave blank

@crawlee/playwright (PlaywrightCrawler)

Issue description

After I build a dockerfile with template Dockerfile, and I start project by ENTRYPOINT [ "node" ] in dockerfile, for running custom file enterpoint

It works well by runing tsx src/filename.ts or node dist/filename.js in local. But time out when run docker run my-build-image dist/filename.js

request: Request {
    id: 'rYNmq8qczeMRg0W',
    url: 'https://www.ali213.net/news/new/',
    loadedUrl: undefined,
    uniqueKey: 'https://www.ali213.net/news/new',
    method: 'GET',
    payload: undefined,
    noRetry: false,
    retryCount: 0,
    errorMessages: [
      'Error: requestHandler timed out after 130 seconds (rYNmq8qczeMRg0W).\n' +
        '    at Timeout._onTimeout (/home/myuser/node_modules/@apify/timeout/cjs/index.cjs:64:68)\n' +
        '    at listOnTimeout (node:internal/timers:581:17)\n' +
        '    at process.processTimers (node:internal/timers:519:7)'
    ],
    headers: {},
    userData: [Getter/Setter],
    handledAt: undefined
  },

Code sample

No response

Package version

3.11.2

Node.js version

v20.10.0

Operating system

No response

Apify platform

• Tick me if you encountered this issue on the Apify platform

I have tested this on the next release

No response

Other context

No response

[B4nan]

The request to https://www.ali213.net/news/new times out, try to use some proxies or a browser based crawler.

Hard to help without seeing more details, but this is not a bug in the library, its a problem with your setup (and the target site). Could be as well caused by different fingerprints used locally and inside the docker if you use a browser based crawler already.

[Ardear]

Is't the PlaywrightCrawler a browser based crawler? And i build image from apify/actor-node-playwright-chrome:20.
Docker file use the example file :https://crawlee.dev/docs/guides/docker-images#example-dockerfile Browser+TypeScript

[B4nan]

if you use playwright, then the entrypoint shouldnt be just node, you need to start the x server first.

https://github.com/apify/apify-actor-docker/blob/master/node-playwright-chrome/Dockerfile#L114

either way, if you need more help, you need to provide a complete reproduction

[Ardear]

Thank you, that's my problem.

[B4nan]

Maybe it's connected to this apify/apify-actor-docker#139

Looks like the X server is now required even for headless runs. We will investigate that.