Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Vlatombe opened this issue May 30, 2024 · 3 comments
Closed

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

Vlatombe opened this issue May 30, 2024 · 3 comments
Assignees
Labels

Comments

@Vlatombe
Copy link
Member

Jenkins and plugins versions report

Environment
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 microsoft/Windows-Containers#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
Copy link
Member

jglick commented May 30, 2024

Resolved by #816 (at least for now)?

@dduportal
Copy link
Contributor

Resolved by #816 (at least for now)?

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

@lemeurherve
Copy link
Member

lemeurherve commented Jul 10, 2024

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

From microsoft/Windows-Containers#493 (comment):

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants