Skip to main content
Home/Recipes/Docker and CI pipeline extraction
Automation

Docker and CI pipeline extraction

Developer

Overview

Chromium fails in Docker and most CI environments without --no-sandbox. Add this flag to any pipeline step that runs Dembrandt in a container.

Headless Chromium requires kernel-level sandboxing that is unavailable in most Docker containers and CI environments. Without --no-sandbox, the extraction crashes on startup. The flag disables the browser sandbox, which is safe in isolated container environments where the OS-level isolation already provides equivalent protection. Combine with --json-only to pipe the output directly into a file or another pipeline step without writing to disk.

Basic CI extraction

Terminal
dembrandt app.example.com --no-sandbox --json-only > tokens.json

Save output in CI

Terminal
dembrandt app.example.com --no-sandbox --save-output
GitHub Actions step
- name: Extract design tokens
run: |
npx dembrandt ${{ env.SITE_URL }} --no-sandbox --json-only > tokens.json
- name: Upload tokens
uses: actions/upload-artifact@v4
with:
name: design-tokens
path: tokens.json
Output

Successful extraction in Docker or CI. No sandbox crash.

More in Automation

Track token driftCI/CD drift detectionDesign drift detection in GitHub ActionsCI drift gate (GitHub Actions)

Browse all

All recipes →

52 workflows

Continue reading

Getting started

Install Dembrandt and turn any public website into a complete set of design tokens in under 2 minutes. All you need is Node.js and a terminal.

Read more

MCP

Use Dembrandt as a tool inside Claude Code, Cursor, Windsurf, or any MCP-compatible editor. Your agent extracts live design tokens automatically when you ask.

Read more

Skills

30 UX and design system skills for AI agents. Install once, your agent designs with hierarchy, WCAG standards, and brand accuracy. The UX knowledge that normally costs senior consultant days.

Read more