Use absolute path for ./tmp/chromium/flags

[juecd]

Running Docker locally requires an absolute path for .tmp/chromium/flags"

---

---

TL;DR

Updated run-docker.sh to use an absolute path for Chromium flags, fixing local Docker execution.

Why we made these changes

Local Docker setup for Chromium failed because the flags file was not found without an absolute path.

What changed?

• images/chromium-headful/run-docker.sh: Modified the FLAGS_FILE variable to prepend $(pwd)/, ensuring it's always an absolute path relative to the current working directory.

Validation

• Verified local Docker execution works correctly with the absolute path.
• No testing was performed with unikernels.
  

[mesa-dot-dev]

What Changed

This PR updates the images/chromium-headful/run-docker.sh script to use an absolute path for the Chromium flags file. The FLAGS_FILE variable is now prepended with $(pwd)/ to ensure it's correctly resolved when running Docker locally, fixing a pathing issue.

Risks / Concerns

This is a low-risk change that improves the local development experience. The author noted that this was not tested with unikernels, which is a minor concern to keep in mind, but the change itself is robust. Great work on this fix!

^{1 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings}