search

jenkinsci / docker-agent

Jenkins agent (base image) and inbound agent Docker images
https://hub.docker.com/r/jenkins/inbound-agent/
MIT License
282 stars 228 forks source link

Unable to build an extension of inbound-agent:*ltsc2019 #815

Closed Vlatombe closed 3 months ago

Vlatombe commented 3 months ago

Jenkins and plugins versions report

Environment ```text Paste the output here ```

What Operating System are you using (both controller, and any agents involved in the problem)?

N/A

Reproduction steps

N/A

Expected Results

The image build succeeds

Actual Results

Getting the following error when extending the image

#8 [2/2] COPY agent.jar C:/ProgramData/Jenkins/agent.jar
--
  | 110707 | 01:09:48 PM | #8 ERROR: mount callback failed on /tmp/containerd-mount2303027507: link /tmp/containerd-mount2303027507/Windows/INF/basicrender.inf /tmp/containerd-mount2303027507/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory

Anything else?

I'm hitting https://github.com/microsoft/Windows-Containers/issues/493 when trying to extend the inbound-agent image built for ltsc2019 (using docker buildx on linux host).

This was not happening with previous versions. From the issue referenced above, a workaround (until Microsoft fixes the upstream issue) is to pin the base windows image to the April release

Are you interested in contributing a fix?

No response

jglick commented 3 months ago

Resolved by #816 (at least for now)?

dduportal commented 3 months ago

Resolved by #816 (at least for now)?

Absolutely! I was waiting for the images to be fully released before closing, which is done:

lemeurherve commented 1 month ago

I'm checking that the last image published today effectively fix the issue to update the pinned image version.

From https://github.com/microsoft/Windows-Containers/issues/493#issuecomment-2219090926:

The updated images released as part of the July 2024 security update today include the fix for this issue.