Open mihkeleidast opened 1 month ago
Okay, I at least figured out a workaround.
Something seems to have happened to how the CHROMIUM_FLAGS
env variable is passed forward, as that's what has stopped working in the same way.
The flags work if passed as args/command to the image, but that is not possible yet with GitHub Actions service containers.
So I tested If perhaps I can just run the container manually... and it works! Example run: https://github.com/mihkeleidast/chromium-service-container-debug/actions/runs/10106859331/job/27949698933
I would still appreciate if someone looked at why the env variable is no longer respected
Describe the bug When using this container in GitHub Actions as a service, it exits immediately after starting since version 108, example: https://github.com/mihkeleidast/chromium-service-container-debug/blob/main/.github/workflows/test.yml
It works as expected (e.g. container stays running in the background) until version 102, example: https://github.com/mihkeleidast/chromium-service-container-debug/actions/runs/10083423138/job/27879954595
To Reproduce Steps to reproduce the behavior:
What is the expected behavior? Container should stay running in the background so I can run tests via puppeteer in the main runner.
What is the actual behavior? Container exits immediately after starting.
Possible solution I don't know if it helps much, but for example chromedp/headless-shell stays running as expected if used in the same way.
Logs
From the test run:
Versions See in the logs above.
Additional context
I tried various different settings and options, but could not get it to keep running on newer versions. Any pointers appreciated.