[vs] Add knob to skip DASH engine image install#27346
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI note for #27346: the The log shows
This PR only gates whether |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
5526adb to
99b8bac
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI failure looks unrelated to this PR (#27346):
Saved log excerpt: |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI failure classification for #27346: Azure build The source changes in this PR do not touch |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI classification for #27346: Azure build 1113201 failed required |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Rustiqly <rustiqly@users.noreply.github.com>
99b8bac to
8170b3e
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI failure looks unrelated to this PR. Azure build
Logs saved locally for tracking:
Re-running Azure. |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI classification for #27346: latest Azure build Re-running Azure to get a clean required-check result. |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI classification for #27346: Azure build The failure is unrelated to this PR's VS DASH install knob. The docker-ptf Trivy scan reported generated/base image findings only: Saved log: |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Why I did it
VS images currently always install
docker-dash-engine.gz, even when the user is trying to build a smaller/resource-constrained VS image and does not need DASH engine services. In a recent VS image-size investigation for #26636,docker-dash-engine.gzshowed up as a clear optional payload candidate at roughly 167 MB in the image artifacts.How I did it
Added
INCLUDE_VS_DASH_ENGINE ?= yand used it to gate onlySONIC_INSTALL_DOCKER_IMAGESfordocker-dash-engine.gz.The default remains
y, so existing VS builds are unchanged. SettingINCLUDE_VS_DASH_ENGINE=nstill allows the docker image target to be built if requested, but skips installing it into the final VS image.How I verified it
Output:
Fixes #26636.