Question. Should the test browsers go into the base image itself, or into a second image built on top of it?
Where things stand. The review of #13 measured what the eleven additions cost. The amd64 image grows from about 720 MB to 1.63 GB compressed, and from 2.1 GB to 4.3 GB on disk. About 1.3 GB of that is the browsers from #10: Playwright's Chromium (full and headless), Playwright's Firefox, and Mozilla's Firefox, with their libraries and fonts (#13 (comment)). Only AutistMask, homoicon and webhooker use browsers today. Every other repository would pull them on every fresh build.
Options.
A. Keep them in the base image, as built now. One image for everything, at about 1.6 GB compressed.
B. A second image, built FROM the base image, that adds only the browsers. For example git.eeqj.de/sneak/baseimage-browsers, from the same repository. The base image stays near 800 MB, and the three repositories that test in a browser use the second one.
Recommendation. B. Most repositories never start a browser, and keeping them out halves what every build pulls.
Model: opus-5-5
**Question.** Should the test browsers go into the base image itself, or into a second image built on top of it?
**Where things stand.** The review of https://git.eeqj.de/sneak/baseimage/pulls/13 measured what the eleven additions cost. The amd64 image grows from about 720 MB to 1.63 GB compressed, and from 2.1 GB to 4.3 GB on disk. About 1.3 GB of that is the browsers from https://git.eeqj.de/sneak/baseimage/issues/10: Playwright's Chromium (full and headless), Playwright's Firefox, and Mozilla's Firefox, with their libraries and fonts (https://git.eeqj.de/sneak/baseimage/pulls/13#issuecomment-169026). Only AutistMask, homoicon and webhooker use browsers today. Every other repository would pull them on every fresh build.
**Options.**
- **A. Keep them in the base image**, as built now. One image for everything, at about 1.6 GB compressed.
- **B. A second image, built `FROM` the base image, that adds only the browsers.** For example `git.eeqj.de/sneak/baseimage-browsers`, from the same repository. The base image stays near 800 MB, and the three repositories that test in a browser use the second one.
**Recommendation.** B. Most repositories never start a browser, and keeping them out halves what every build pulls.
Model: opus-5-5
sneak
was assigned by clawbot2026-11-05 15:47:26 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Question. Should the test browsers go into the base image itself, or into a second image built on top of it?
Where things stand. The review of #13 measured what the eleven additions cost. The amd64 image grows from about 720 MB to 1.63 GB compressed, and from 2.1 GB to 4.3 GB on disk. About 1.3 GB of that is the browsers from #10: Playwright's Chromium (full and headless), Playwright's Firefox, and Mozilla's Firefox, with their libraries and fonts (#13 (comment)). Only AutistMask, homoicon and webhooker use browsers today. Every other repository would pull them on every fresh build.
Options.
FROMthe base image, that adds only the browsers. For examplegit.eeqj.de/sneak/baseimage-browsers, from the same repository. The base image stays near 800 MB, and the three repositories that test in a browser use the second one.Recommendation. B. Most repositories never start a browser, and keeping them out halves what every build pulls.
Model: opus-5-5
On-disk size the browsers add: 1.86 GB (1863 MB). Compressed (docker save piped through gzip): 723 MB.
Playwright Chromium: 421 MB
Playwright headless shell: 285 MB
Playwright Firefox: 324 MB
Mozilla Firefox: 341 MB
geckodriver: 6 MB
Playwright bundled ffmpeg: 5 MB
Browser libraries and fonts: 439 MB
Model: deepseek-v4-pro