chore(docker): add Playwright Chromium prerequisites

[thesobercoder]

This PR adds missing Debian system libraries required for Playwright/Chromium to run inside the Automaker Docker images, and documents an optional cache volume for persisting downloaded Playwright browsers.

Changes:

• Install Playwright/Chromium runtime dependencies in Dockerfile (server image)
• Install the same dependencies in Dockerfile.dev (dev image)
• Add an example playwright-cache volume mount and volume definition stub in docker-compose.override.yml.example to persist /home/automaker/.cache/ms-playwright

Why:
E2E tests (and any browser automation) rely on Playwright + Chromium. Without these system libraries, Chromium can fail to launch in slim Debian images.

Summary by CodeRabbit

• Chores
  • Updated container build configurations to include system dependencies for browser automation support in production and development environments.
  • Added optional cache persistence guidance in development setup documentation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Important

Review skipped

Too many files!

15 files out of 165 files are above the max files limit of 150.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

📝 Walkthrough

Walkthrough

The pull request adds Playwright/Chromium system dependencies to Docker configuration files (Dockerfile, Dockerfile.dev) and includes commented example volume guidance in docker-compose.override.yml.example for optional Playwright cache persistence.

Changes

Cohort / File(s)	Summary
Docker dependency updates Dockerfile, Dockerfile.dev	Added Playwright/Chromium system dependencies to apt-get install commands in both production and development Docker images
Compose file example docker-compose.override.yml.example	Added commented top-level volumes block and commented volume mount example for optional playwright-cache persistence (non-functional documentation)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• feat: add support for external server mode with Docker integration #376: Modifies Dockerfile.dev directly, impacting the same Docker development image configuration.
• feat: Add Docker containerization for secure, isolated execution #179: Updates Docker-related configuration files (Dockerfiles and docker-compose.override.yml.example) for container-based browser automation support.

Suggested labels

Bug, Ready-To-Merge

Suggested reviewers

• webdevcody

Poem

🐰 A rabbit hops through Docker files with glee,
Adding browser tools for Playwright to be free,
Chrome's system libs now bundled with care,
In dev and production, dependencies fair! 🎭

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(docker): add Playwright Chromium prerequisites' clearly and specifically summarizes the main change: adding necessary system dependencies for Playwright/Chromium across Docker configurations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @thesobercoder, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Docker images by integrating necessary system dependencies for Playwright and Chromium, resolving potential runtime issues in slim Debian environments. Additionally, it provides a documented method for users to persist Playwright browser installations, which will significantly reduce setup time and bandwidth for end-to-end testing and browser automation workflows.

Highlights

• Dockerfile Updates: Added essential Debian system libraries for Playwright/Chromium to both the main "Dockerfile" and "Dockerfile.dev" to ensure browser automation runs correctly in slim images.
• Playwright Cache Persistence: Introduced an example "playwright-cache" volume mount and definition in "docker-compose.override.yml.example" to allow persistence of downloaded Playwright browsers across container restarts, optimizing development workflow.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly adds the necessary system dependencies for Playwright/Chromium to the Docker images and provides a helpful example for caching downloaded browsers. My review includes suggestions to improve the maintainability of the Dockerfiles by sorting the long list of new packages. I've also identified and suggested a fix for an indentation issue in the docker-compose.override.yml.example file that would cause errors for users who uncomment the new volume definition. Overall, these are good changes that improve the development and testing experience.

[gemini-code-assist]

The indentation of this commented-out volume definition is incorrect. If a user uncomments these lines as-is, it will result in a YAML syntax error. Top-level keys in docker-compose.yml files (like volumes) should have their direct children indented by two spaces.

  # Playwright cache volume (persists Chromium installs)
  # playwright-cache:
  #   name: automaker-playwright-cache

[gemini-code-assist]

For better readability and maintainability, it's good practice to sort package lists alphabetically. This makes it easier to see what's included and to spot duplicates or missing packages in the future.

    fonts-liberation libasound2 libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libcairo2 \
    libcups2 libdbus-1-3 libdrm2 libexpat1 libfontconfig1 libgbm1 \
    libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 \
    libpangoft2-1.0-0 libu2f-udev libvulkan1 libx11-6 libx11-xcb1 libxcb1 \
    libxcomposite1 libxdamage1 libxext6 libxfixes3 libxkbcommon0 libxrandr2 \
    libxrender1 libxshmfence1 libxss1 libxtst6 xdg-utils \

[gemini-code-assist]

For better readability and maintainability, it's good practice to sort this package list alphabetically.

Additionally, this list of dependencies is now duplicated between Dockerfile and Dockerfile.dev. To avoid them getting out of sync in the future, you might consider extracting this list into a shared script in the scripts/ directory as part of a future refactoring.

    fonts-liberation libasound2 libatk-bridge2.0-0 libatk1.0-0 libatspi2.0-0 libcairo2 \
    libcups2 libdbus-1-3 libdrm2 libexpat1 libfontconfig1 libgbm1 \
    libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 \
    libpangoft2-1.0-0 libu2f-udev libvulkan1 libx11-6 libx11-xcb1 libxcb1 \
    libxcomposite1 libxdamage1 libxext6 libxfixes3 libxkbcommon0 libxrandr2 \
    libxrender1 libxshmfence1 libxss1 libxtst6 xdg-utils \

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@docker-compose.override.yml.example`:
- Around line 34-37: The top-level volumes block has excessive indentation for
the commented volume definition; un-indent the commented lines so they align
under the top-level "volumes:" key with two spaces (i.e., adjust
"playwright-cache:" and "name: automaker-playwright-cache" to the same
indentation level as other top-level entries) so users can safely uncomment
without YAML indentation errors.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0dc70ad and 7f9ca26.

📒 Files selected for processing (3)

• Dockerfile
• Dockerfile.dev
• docker-compose.override.yml.example

🔇 Additional comments (3)

Dockerfile.dev (1)

11-21: LGTM! Playwright dependencies are well-documented.

The system library list correctly covers Playwright/Chromium runtime requirements for Debian-slim images. The inline comment clarifies the purpose, aiding future maintainability.

docker-compose.override.yml.example (1)

19-21: LGTM! Helpful documentation for Playwright cache persistence.

The commented example clearly explains the volume mount purpose and usage workflow. This provides good guidance without forcing configuration on users.

Dockerfile (1)

63-72: LGTM! Dependencies align with Dockerfile.dev.

The package list correctly mirrors Dockerfile.dev, ensuring consistency across development and production images. The inline comment clarifies the purpose.

Consider whether Playwright dependencies are needed in the production image. If browser automation is only used during development/testing, these libraries (~40-60MB) could be omitted from the production stage to reduce image size. However, if runtime browser automation (e.g., scraping, PDF generation) is a production feature, keeping them is appropriate.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}