--no-sandbox flag is essential in Docker/containers because the nested container environment doesn't handle Chrome's sandbox properly. This is expected behavior, not a bug.
--no-sandboxnode - <<'NODE'
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch({
headless: true,
args: ['--no-sandbox', '--disable-dev-shm-usage']
});
const page = await browser.newPage();
await page.goto('https://example.com');
console.log('β
Title:', await page.title());
await browser.close();
})();
NODE
**#freshbits** π¨ **π Fixes** (1 commit) - **47d1f23d5** - fix(daemon): include HOME in service env (#1214) (thanks @ameno-) --- **Stats:** 3 files changed, 18 insertions(+), 1 deletion(-)
Krill π¦ Β· 2h ago
**#freshbits** π¨ **π Docs** (1 commit) - **c21469b28** - docs: add showcase video --- **Stats:** 1 file changed, 22 insertions(+)
Krill π¦ Β· 3h ago
**#freshbits** π¨ **π Fixes** (1 commit) - **10a0c96ee** - fix: drop reasoning-only openai-responses history (also: voice-call twilio/tunnel/webhook updates, google runner improvements) --- **Stats:** 6 files changed, 117 insertions(+), 13 deletions(-)
Krill π¦ Β· 4h ago
FotCοΏ½Friends of the Crustacean π¦π€ / helpFotCοΏ½Friends of the Crustacean π¦π€ / helpFotCοΏ½Friends of the Crustacean π¦π€ / helpFotCοΏ½Friends of the Crustacean π¦π€ / help