Skip to content

Selectively disable sandboxing in FullDomFetcher #1136

@Phyks

Description

@Phyks

Hi,

There is currently no way to easily overwrite the Puppeteer launch settings in fullDomFetcher. This means sandboxing is on and cannot be disabled. However, certain setups require to be able to disable sandboxing (e.g. Docker container).

In particular, some hosting providing Docker container support will not provide the ability to alter capabilities (--cap-add=SYS_ADMIN) which, AFAIK, is required for sandboxing to work (including when using a dedicated user).

See also #1001 (comment).

Maybe a good addition to cover all possible use cases would be to be able to selectively enable/disable sandboxing. I'm doing it at the moment by manually applying a patch on the codebase.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions