I noticed docker compose is now telling me I can set COMPOSE_BAKE=true for “better performance”.

Does anyone have any experience with this? Is it worth it? I get suspicious when a program tells me “just use this, it has better performance”, but it’s not the default.

  • yarr@feddit.nlOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 days ago

    I did read the docs. My question is more about the actual user experience, like has any team used this? Building images is not a bottleneck of mine and most of my projects are small, so I was curious with the discrepancy between:

    1. Docker compose cares enough about this to pollute every build output with an ‘advertisement’ for it
    2. It’s not the default?

    When I see something like that, I get curious. If you haven’t tried it, that’s fair. Just looking to hear from a user, happy or not.

    • madame_gaymes
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 days ago

      From the way you worded the post, it didn’t seem like you had looked into it very much. If you want to compare to similar experiences, this looks to me like Docker’s version of a lockfile.

      They don’t even use the actual word “performance” on any of the doc pages for Bake, so the build output thing is very poorly worded, and it sucks that they feel the need to put it in build output.

      • yarr@feddit.nlOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 days ago

        and it sucks that they feel the need to put it in build output.

        I agree. I treat that as holy ground. If it doesn’t have really large implications, I do NOT want to see it in the output. Reminds me of installing things in npm and seeing all the little ‘shoutouts’.