Skip to content

Update non AzLinux Packages in Tools Image#628

Open
ComradeCow wants to merge 4 commits into
masterfrom
skool/update-3p-in-tools-image
Open

Update non AzLinux Packages in Tools Image#628
ComradeCow wants to merge 4 commits into
masterfrom
skool/update-3p-in-tools-image

Conversation

@ComradeCow

Copy link
Copy Markdown
Member

Adds steps in the Tools image to update dependencies that are distributed outside the AzLinux package feed. This will help us keep vulnerabilities down to an absolute minimum. We want to minimize the work done in the Tools image as it affects the image pull performance more than changes in the Base image, but we need more frequent updates to keep the image secure.

Update steps added for:

  • Terraform
  • azd
  • Microsoft 365 CLI
  • Ruby gems

Intentionally skipped updates for:

  • Bicep - there isn't a reliable "check for updates" mechanism. We've yet to see it show up on our vulnerability scans, so making sure its up-to-date is less pressing.
  • ansible-galaxy collections - they also don't show in the vulnerability scans, so less pressing to upgrade.

@ComradeCow ComradeCow changed the title Skool/update 3p in tools image Update non AzLinux Packages in Tools Image Jun 12, 2026
@codekrafter

Copy link
Copy Markdown
Member

Have we checked best/worst case size impact for this?

Comment thread linux/base.Dockerfile
#
npm install -q -g @pnp/cli-microsoft365 && \
npm install -q -g @pnp/cli-microsoft365 \
&& m365 version && \

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do we use this version check for?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to output data to stdout, similar to some of the other installs. When I was testing the update logic, I had to hop into the image to find the version. Having it show in the output made that particular step faster.

@ComradeCow

Copy link
Copy Markdown
Member Author

Have we checked best/worst case size impact for this?

Best case its zero because there are no new updates and there have been no releases since the last base image was built.

Worst case, it probably can be a lot. Locally I ran that and ended up with this layer at 617MB. I think that updated everything but I'm not certain.

I know this will increase the image size, which is why the steps are careful to only update if its needed. Our goal is to get releases rolling often enough where generally this layer is small. The dependencies in that list update (generally) monthly. So I expect in most cases there won't be updates available to pull in. But if there are, this change will help us keep our Vulnerability dashboards more clean.

@github-actions

Copy link
Copy Markdown
Contributor

Image size with this change is base: 6127MB, tools: 9780MB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants