Description

onedr0p

opened on May 20, 2026

Issue body actions

Description

Hi 👋

In my current docker bake definitions I have zstd,force-compression=true, would it be possible to add an input to customize these?

Example:

https://github.com/home-operations/containers/blob/4013a5f13892cb1ea96557f04ea59ccc21ce796a/.github/workflows/app-builder.yaml#L146-L156

I would be willing to contribute the change if this is accepted.

Reacted by Steve Jacobs and AFCMS

Activity

1. onedr0p

   added

   kind/enhancementNew feature or requestNew feature or request

   status/triage

   on May 20, 2026
2. onedr0p

   changed the title [-]Add support for compression settings[/-] [+]Add support for compression settings in bake action[/+] on May 20, 2026
3. crazy-max commented on Jul 2, 2026

   

   crazy-max

   on Jul 2, 2026

   Member

   More actions

   Yes I think we could add an input for both bake and build. Will think about the UX.

   Reacted by Devin Buhl, Steve Jacobs and AFCMS
4. crazy-max

   removed

   status/triage

   on Jul 2, 2026
5. AFCMS

   marked this as blocking on Oct 21, 2026

   • Reduce Docker image size oktomusic/oktomusic#263
6. onedr0p commented on Nov 3, 2026

   

   onedr0p

   on Nov 3, 2026

   Author

   More actions

   @crazy-max I made a proposal on a branch: main...onedr0p:github-builder:build-bake-compression

   The branch adds three inputs to build.yml and bake.yml: compression, compression-level, and force-compression. Each input has the same name as an attribute of the BuildKit image exporter. compression accepts uncompressed, gzip, estargz, or zstd.

   The prepare job makes sure that compression is one of these four values and that compression-level contains only digits. Because of this, the inputs cannot add other attributes to the exporter. The inputs apply only to output: image. For output: local, the workflow ignores them and logs a warning. With the default values, the output string does not change.

   The new tests use a fixture with a final stage that keeps the gzip base layer of alpine. The zstd test passes only when force-compression converts that layer.

   I ran the same jobs from my fork. I turned off signing for these runs, because the signing step expects the identity of the docker/github-builder workflow. The results for both platforms were:

   • With zstd and force-compression, all layers were zstd for build and bake.
   • With zstd only, the base layer stayed gzip and the new layer was zstd.
   • With the default values, all layers stayed gzip.

   I can open a PR now. If you prefer a different UX, for example a single input, I can change the branch.
7. onedr0p commented on Nov 3, 2026

   

   onedr0p

   on Nov 3, 2026

   Author

   More actions

   I went ahead and open the PR instead: #333

Issue actions