Skip to content

Document Ferrum's Docker container mode - #323

Merged
route merged 3 commits into
rubycdp:mainfrom
ablzh:patch-1
Aug 21, 2026
Merged

Document Ferrum's Docker container mode#323
route merged 3 commits into
rubycdp:mainfrom
ablzh:patch-1

Conversation

@ablzh

@ablzh ablzh commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace the explicit no-sandbox example with Ferrum's dockerize: true
    option
  • clarify that container mode is needed only when Chrome or Chromium cannot
    use its sandbox
  • recommend keeping the browser sandbox enabled when the container supports it

Why

Ferrum 0.17.2 introduced the dockerize: true option in
rubycdp/ferrum#561.
The same change updated Ferrum's Docker documentation to use dockerize: true
instead of configuring no-sandbox manually.

Cuprite's browser inherits from Ferrum::Browser and passes its driver options
to Ferrum, so the option can be used directly in the Cuprite driver
configuration. The current Cuprite README still shows the older manual option
and implies that disabling the sandbox is required for every Docker setup.

This change aligns the Cuprite documentation with Ferrum's current container
API while making it clear that the browser sandbox should remain enabled when
the container supports it.

References

Testing

Documentation-only change. No automated tests were run.

ablzh added 3 commits August 21, 2026 14:53
Updated Docker usage instructions for Cuprite driver to include Ferrum's container mode and clarified the no-sandbox option usage.
Updated instructions for using Chrome in Docker with Cuprite, emphasizing Ferrum's container mode and removing redundant options.
Clarify usage of Ferrum's container mode and browser options.
@route

route commented Aug 21, 2026

Copy link
Copy Markdown
Member

Thanks!

@route
route merged commit a1e9fc9 into rubycdp:main Aug 21, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants