[Build] Add flag to revert to glibc 2.42 memory management#255699
Conversation
|
Project deployed, see credentials at: https://buildkite.com/elastic/kibana-deploy-project-from-pr/builds/1124 |
| provider: gcp | ||
| image: family/kibana-ubuntu-2404 | ||
| imageProject: elastic-images-prod | ||
| machineType: n2-standard-2 |
There was a problem hiding this comment.
This was quite slow and hitting timeouts sometimes. I've bumped the machines quite substantially for better DX. Running this pipeline shouldn't be almost an hour.
| if (flags.baseImage === 'wolfi') | ||
| baseImageName = | ||
| 'docker.elastic.co/wolfi/chainguard-base:latest@sha256:b5a03b6a754fa2f9a29e44e316a6c4df1f606cd8a3cd8810ce3d6a3a3134428b'; | ||
| 'docker.elastic.co/wolfi/chainguard-base:latest@sha256:b2134dbfbcfb987eec9c249fc81111963de596ff76098775c2444a2869401d9c'; |
There was a problem hiding this comment.
This is the most recent (as of March 30) Wolfi image and required to bump to have glibc 2.43 active for testing.
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
Cloud deployment initiated, see credentials at: https://buildkite.com/elastic/kibana-deploy-cloud-from-pr/builds/892 |
ApprovabilityVerdict: Needs human review This PR modifies production Docker image configuration by adding a glibc memory allocation tunable and updating the base image, which affects runtime behavior. All changed files are owned by @elastic/kibana-operations and should be reviewed by the designated code owners. You can customize Macroscope's approvability policy. Learn more. |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
Historycc @Ikuni17 |
|
Starting backport for target branches: 8.19, 9.2, 9.3 https://github.com/elastic/kibana/actions/runs/23814226349 |
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
…55699) ## Summary Reverts elastic#255691 Newer Chainguard images updated to `glibc 2.43` which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates. See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details. (cherry picked from commit 9f346df) # Conflicts: # src/dev/build/tasks/os_packages/docker_generator/run.ts # src/dev/build/tasks/os_packages/docker_generator/templates/base/Dockerfile
…55699) ## Summary Reverts elastic#255691 Newer Chainguard images updated to `glibc 2.43` which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates. See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details. (cherry picked from commit 9f346df) # Conflicts: # src/dev/build/tasks/os_packages/docker_generator/run.ts # src/dev/build/tasks/os_packages/docker_generator/templates/base/Dockerfile
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…55699) ## Summary Reverts elastic#255691 Newer Chainguard images updated to `glibc 2.43` which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates. See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details. (cherry picked from commit 9f346df) # Conflicts: # src/dev/build/tasks/os_packages/docker_generator/run.ts # src/dev/build/tasks/os_packages/docker_generator/templates/base/Dockerfile
…55699) (#260565) # Backport This will backport the following commits from `main` to `8.19`: - [[Build] Add flag to revert to glibc 2.42 memory management (#255699)](#255699) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-03-31T18:54:10Z","message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","ci:cloud-deploy","ci:cloud-redeploy","ci:project-deploy-elasticsearch","ci:project-redeploy","v9.4.0"],"title":"[Build] Add flag to revert to glibc 2.42 memory management","number":255699,"url":"https://github.com/elastic/kibana/pull/255699","mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/255699","number":255699,"mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}}]}] BACKPORT-->
…5699) (#260564) # Backport This will backport the following commits from `main` to `9.2`: - [[Build] Add flag to revert to glibc 2.42 memory management (#255699)](#255699) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-03-31T18:54:10Z","message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","ci:cloud-deploy","ci:cloud-redeploy","ci:project-deploy-elasticsearch","ci:project-redeploy","v9.4.0"],"title":"[Build] Add flag to revert to glibc 2.42 memory management","number":255699,"url":"https://github.com/elastic/kibana/pull/255699","mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/255699","number":255699,"mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}}]}] BACKPORT-->
…5699) (#260563) # Backport This will backport the following commits from `main` to `9.3`: - [[Build] Add flag to revert to glibc 2.42 memory management (#255699)](#255699) <!--- Backport version: 11.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-03-31T18:54:10Z","message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","ci:cloud-deploy","ci:cloud-redeploy","ci:project-deploy-elasticsearch","ci:project-redeploy","v9.4.0"],"title":"[Build] Add flag to revert to glibc 2.42 memory management","number":255699,"url":"https://github.com/elastic/kibana/pull/255699","mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/255699","number":255699,"mergeCommit":{"message":"[Build] Add flag to revert to glibc 2.42 memory management (#255699)\n\n## Summary\n\nReverts #255691\n\nNewer Chainguard images updated to `glibc 2.43` which changes memory\nallocation behavior. Adding this flag reverts that behavior and allows\nus to unblock Chainguard image updates.\n\nSee\nhttps://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ\nfor more details.","sha":"9f346df20cdb34f0792201cd70a5274a8f03995d"}}]}] BACKPORT-->
…55699) ## Summary Reverts elastic#255691 Newer Chainguard images updated to `glibc 2.43` which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates. See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details.
…55699) ## Summary Reverts elastic#255691 Newer Chainguard images updated to `glibc 2.43` which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates. See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details.
Summary
Reverts #255691
Newer Chainguard images updated to
glibc 2.43which changes memory allocation behavior. Adding this flag reverts that behavior and allows us to unblock Chainguard image updates.See https://groups.google.com/a/elastic.co/g/support_team/c/RBgzGXEdyR8/m/MxtQhaAmCQAJ for more details.