FROM/layer-extraction on ltsc2019 fails: link operation for `Windows/INF/basicrender.inf` on cross-platform building from Linux #493

markmandel · 2024-05-14T23:11:01Z

Describe the bug

COPY commands have been working normally for years with our lts2019 windows container build on Agones, but started failing today with an error message of:

Dockerfile.windows:18
--------------------
  16 |     FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}
  17 |
  18 | >>> COPY ./bin/sdk-server.windows.amd64.exe /agones/sdk-server.exe
  19 |     COPY ./bin/LICENSES ./bin/dependencies-src.tgz /agones/
  20 |
--------------------
ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount3356703247: link /tmp/containerd-mount3356703247/Windows/INF/basicrender.inf /tmp/containerd-mount3356703247/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory
make: *** [Makefile:619: build-agones-sdk-image-windows-ltsc2019] Error 1

Where ${WINDOWS_VERSION} is ltsc2019

To Reproduce

To reproduce this, just try copying something in:

ARG WINDOWS_VERSION=ltsc2019
FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}

COPY ./emptyfile /emptyfile

(Assuming you have a buildx builder already)

❯ touch emptyfile
❯ docker buildx build --platform windows/amd64 --builder windows-builder-ltsc2019 --tag=windows-test .
[+] Building 18.6s (6/6) FINISHED                                                                                                                                                                                                                                                                                                              docker-container:windows-builder-ltsc2019
 => [internal] load build definition from Dockerfile                                                                                                                                                                                                                                                                                                                                0.1s
 => => transferring dockerfile: 156B                                                                                                                                                                                                                                                                                                                                                0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019                                                                                                                                                                                                                                                                                                      0.1s
 => [internal] load .dockerignore                                                                                                                                                                                                                                                                                                                                                   0.0s
 => => transferring context: 2B                                                                                                                                                                                                                                                                                                                                                     0.0s
 => [internal] load build context                                                                                                                                                                                                                                                                                                                                                   0.0s
 => => transferring context: 28B                                                                                                                                                                                                                                                                                                                                                    0.0s
 => [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:3c97a5c1c32ddb346c190f00a588da6e682a9a8160869f4969edfd7c6e4d1c03                                                                                                                                                                                                                                               18.3s
 => => resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:3c97a5c1c32ddb346c190f00a588da6e682a9a8160869f4969edfd7c6e4d1c03                                                                                                                                                                                                                                                0.0s
 => => extracting sha256:0dd0445527a5079720e935502b31de927b8e22e5ca358026cf0bc8845c5ba5ce                                                                                                                                                                                                                                                                                          18.3s
 => ERROR [2/2] COPY ./emptyfile /emptyfile                                                                                                                                                                                                                                                                                                                                         0.0s
------
 > [2/2] COPY ./emptyfile /emptyfile:
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile:4
--------------------
   2 |     FROM mcr.microsoft.com/windows/servercore:${WINDOWS_VERSION}
   3 |
   4 | >>> COPY ./emptyfile /emptyfile
   5 |
--------------------
ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount1556330329: link /tmp/containerd-mount1556330329/Windows/INF/basicrender.inf /tmp/containerd-mount1556330329/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory

Expected behavior

The image should build 😃

Configuration:

Edition: ltsc2019
Base Image being used: mcr.microsoft.com/windows/servercore
Container engine: docker, Running on Linux (debian).
Container Engine version both 24.x and 26.x

Additional context

You can see a full build output from the Agones build pipeline here: https://console.cloud.google.com/cloud-build/builds/70b984e2-132b-4d1a-915a-862cb03f4830;step=16?e=13803378&project=agones-images

Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked.

The text was updated successfully, but these errors were encountered:

markmandel · 2024-05-15T00:38:17Z

Also possibly worth noting ltsc2022, works still. We tested it!

jsturtevant · 2024-05-15T16:02:53Z

which image is Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked. in reference too?

markmandel · 2024-05-15T16:03:38Z

which image is Using the previous SHA of @sha256:6fdf140282a2f809dae9b13fe441635867f0a27c33a438771673b8da8f3348a4 worked. in reference too?

mcr.microsoft.com/windows/servercore:ltsc2019

markmandel · 2024-05-15T16:04:34Z

For reference, we have this PR now in place to unblock CI: googleforgames/agones#3829

claudiubelu · 2024-05-15T16:06:25Z

Tried it myself on a build node I have been using for years, though I have updated docker buildx since:

docker buildx version
github.com/docker/buildx v0.12.1 30feaa1a915b869ebc2eea6328624b49facd4bfb

I did use this version before KubeCon, and I did use mcr.microsoft.com/windows/servercore:ltsc2019 as a base image for the presentation where I talked about building Windows images. So, I think the image is the issue (Microsoft publishes a new image monthly).

jsturtevant · 2024-05-15T16:09:39Z

This looks to be an issue with the image patches released Yesterday (May 14th). Work around is use April's patch images as done in #493 (comment)

jsturtevant · 2024-05-15T16:12:32Z

/cc @akarshm

jsturtevant · 2024-05-15T16:14:01Z

Adding link to the slack discussion where we narrowed it down to the patch release https://kubernetes.slack.com/archives/C0SJ4AFB7/p1715733067064539

jsturtevant · 2024-05-15T16:14:48Z

/cc @profnandaa

# Description Pin the Windows base images by SHA. A good security practice, but also a fix to the build because the latest servercore:ltsc2019 image is broken. ## Related Issue microsoft/Windows-Containers#493 ## Checklist - [x] I have read the [contributing documentation](https://retina.sh/docs/contributing). - [x] I signed and signed-off the commits (`git commit -S -s ...`). See [this documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) on signing commits. - [x] I have correctly attributed the author(s) of the code. - [x] I have tested the changes locally. - [x] I have followed the project's style guidelines. - [x] I have updated the documentation, if necessary. - [x] I have added tests, if applicable. Signed-off-by: Evan Baker <rbtr@users.noreply.github.com>

profnandaa · 2024-05-18T16:54:56Z

UPDATE: we've been investigating this issue, a few things worth noting:

The issue not actually with COPY but it is happening at the tail-end of FROM and so the reporting just estimates to the next line on the Dockerfile.
The issue is to do with extraction of the latest delta layer on ltsc2019:
```
=> extracting sha256:0dd0445527a5079720e935502b31de927b8e22e5ca358026cf0bc8845c5ba5ce 
```
There's only one "offending" file Windows/INF/basicrender.inf (and its hardlinks); it so happens that on the TAR header (metadata), it's referenced as lowercase basicrender.inf, when the actual file in the layer is BasicRender.inf. Since Windows is not case-sensitive when it comes to files, this issue is only evident when the link operation is done on Linux (which is case-sensitive). Therefore, it reports as file-not-found. RCA is still going on to fix the issue.

PS. will be nice to re-tittle the issue to FROM/layer-extraction on ltsc2019 fails: "mount callback failed"

… until microsoft/Windows-Containers#493 is fixed Signed-off-by: Damien Duportal <damien.duportal@gmail.com>

jsafrane · 2024-06-05T11:50:13Z

Hello, is there any plan / timeline to fix Windows images to be usable on Linux? We as Kubernetes community cannot release our images based on the mcr.microsoft.com/windows/servercore:ltsc2019@latest tag. It's not super critical, at least now, but you never know when a CVE comes and we will need to release images immediately.

profnandaa · 2024-06-05T16:27:47Z

@jsafrane -- a fix is currently going through validation; will update here once it's released.

andriisoldatenko · 2024-06-25T15:51:20Z

hi, @profnandaa, can I gently ask you about a rough ETA for a fix?

ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount1917080101: link /tmp/containerd-mount1917080101/Windows/INF/basicrender.inf /tmp/containerd-mount1917080101/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory Error: Process completed with exit code 1. According to [1], we need to use ltsc2022 as a tag. [1] microsoft/Windows-Containers#493 Signed-off-by: Masashi Honma <masashi.honma@gmail.com>

# Description Pin the Windows base images by SHA. A good security practice, but also a fix to the build because the latest servercore:ltsc2019 image is broken. ## Related Issue microsoft/Windows-Containers#493 ## Checklist - [x] I have read the [contributing documentation](https://retina.sh/docs/contributing). - [x] I signed and signed-off the commits (`git commit -S -s ...`). See [this documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) on signing commits. - [x] I have correctly attributed the author(s) of the code. - [x] I have tested the changes locally. - [x] I have followed the project's style guidelines. - [x] I have updated the documentation, if necessary. - [x] I have added tests, if applicable. Signed-off-by: Evan Baker <rbtr@users.noreply.github.com>

akarshm · 2024-07-10T00:07:52Z

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

profnandaa · 2024-07-10T03:43:42Z

Sure, this is now fixed:

#5 [1/3] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
#5 resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 0.0s done
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 15.73MB / 573.97MB 0.2s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 54.53MB / 573.97MB 0.5s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 93.32MB / 573.97MB 0.8s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 131.07MB / 573.97MB 1.1s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 168.82MB / 573.97MB 1.4s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 206.57MB / 573.97MB 1.7s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 244.32MB / 573.97MB 2.0s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 284.16MB / 573.97MB 2.3s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 322.96MB / 573.97MB 2.6s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 362.81MB / 573.97MB 2.9s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 401.60MB / 573.97MB 3.2s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 442.50MB / 573.97MB 3.5s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 480.25MB / 573.97MB 3.8s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 519.05MB / 573.97MB 4.1s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 559.94MB / 573.97MB 4.4s
#5 sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 573.97MB / 573.97MB 5.2s done
#5 extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e
#5 extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 62.4s done
#5 DONE 67.6s

Guards have been put in place to prevent similar issues from happening in future.

Anyone else can ACK and we can proceed to close the issue.

jsafrane · 2024-07-11T10:40:25Z

I might be doing something wrong, but 41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 does not work for me.

Dockerfile.reproduce:

FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
RUN echo hello world > file

Build output:

docker build -f Dockerfile.reproduce  --platform=windows/amd64 .
[+] Building 458.1s (4/5)                                                                                                                                                                                                                                                                                      docker:default
 => [internal] load build definition from Dockerfile.reproduce                                                                                                                                                                                                                                                           0.0s
 => => transferring dockerfile: 202B                                                                                                                                                                                                                                                                                     0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                                                                                                   0.0s
 => [internal] load .dockerignore                                                                                                                                                                                                                                                                                        0.0s
 => => transferring context: 2B                                                                                                                                                                                                                                                                                          0.0s
 => ERROR [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                                                                                                             457.9s
 => => resolve mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647                                                                                                                                                                                     0.0s
 => => sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 375B / 375B                                                                                                                                                                                                                               0.0s
 => => sha256:f44fdada7eb2e71f80c964b2759421f4f7645a2df97a12aa82f66a8d50410414 596B / 596B                                                                                                                                                                                                                               0.0s
 => => sha256:b51a50ce03f12744163cde05017bec7149d704963fe41aed4b4a78472a98a3f8 788B / 788B                                                                                                                                                                                                                               0.0s
 => => sha256:cb524f6f22159378ea820d234d80ca09b79c2f0cc91315eeef11904e3ff36a21 1.60GB / 1.60GB                                                                                                                                                                                                                         410.6s
 => => sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e 573.97MB / 573.97MB                                                                                                                                                                                                                     219.4s
 => => extracting sha256:cb524f6f22159378ea820d234d80ca09b79c2f0cc91315eeef11904e3ff36a21                                                                                                                                                                                                                               38.1s
 => => extracting sha256:9a0dd2e08eec1795898cdc8ce6217e961b67cb085e11998e2aa5e462cf68eb4e                                                                                                                                                                                                                                8.5s
------
 > [1/2] FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647:
------
WARNING: current commit information was not captured by the build: git was not found in the system: exec: "git": executable file not found in $PATH
Dockerfile.reproduce:1
--------------------
   1 | >>> FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
   2 |     
   3 |     
--------------------
ERROR: failed to solve: failed to register layer: link /Files/Program Files/common files/Microsoft Shared/Ink/en-US/micaut.dll.mui /Files/Program Files (x86)/common files/Microsoft Shared/ink/en-US/micaut.dll.mui: no such file or directory

Fedora 39, with docker-ce-27.0.3-1.fc39.x86_64.

I tried plain mcr.microsoft.com/windows/servercore:ltsc2019, the same result (and the same SHA).

lemeurherve · 2024-07-11T12:44:05Z

@jsafrane I got the same error as you when trying building Windows images with docker build on MacOS.

Try using docker buildx instead:

docker buildx build -f Dockerfile.reproduce --platform windows/amd64 .

jsafrane · 2024-07-11T13:12:44Z

docker buildx build -f Dockerfile.reproduce --platform windows/amd64 .

Same error as docker build.

lemeurherve · 2024-07-11T13:23:05Z

I should have looked more closely your Dockerfile.reproduce: you can't use RUN instructions if you want to build Windows images on another host than Windows.
(See for example https://stackoverflow.com/a/71910784/4074148)

Example of a working Windows Dockerfile built on MacOS:

FROM mcr.microsoft.com/windows/servercore:ltsc2019@sha256:41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647
COPY README.md README.md

jsafrane · 2024-07-12T07:06:07Z

Docker did not even reach RUN, it's stuck at unpacking layers from FROM. It fails with COPY too.

profnandaa · 2024-07-12T18:15:44Z

sorry about that, reopening to investigate.

jsafrane · 2024-07-16T14:36:57Z

It must be some issue in my setup. I can see that Kubernetes is able to build Windows images on Linux based on 41f42aa4ad39d85e4d30642b8111ca6454ca2275f188f012934b9afbaf63a647 and that's what matters to me (logs, search for the SHA there). It was failing with the old image.

/close

akarshm · 2024-07-16T21:15:58Z

Thanks, @jsafrane. Closing this issue.

* Bump golangci-lint to v1.54.2 We upgraded golang lang 1.20 -> 1.21 by commit 9a64023. But according to [2], go1.21 is officially supported since golangci-lint v1.54.1. So, this PR upgrades golangci-lint to v1.54.2. Signed-off-by: Masashi Honma <masashi.honma@gmail.com> * Bump golang version for build to 1.21.11 According to trivy, golang 1.21.4 has trailing vulnerabilities. We upgrade it to 1.21.11 to fix the vulnerabilities. $ trivy image masap20220915/sonobuoy:amd64-v0.57 2024-07-01T09:50:21+09:00 INFO Vulnerability scanning is enabled 2024-07-01T09:50:21+09:00 INFO Secret scanning is enabled 2024-07-01T09:50:21+09:00 INFO If your scanning is slow, please try '--scanners vuln' to disable secret scanning 2024-07-01T09:50:21+09:00 INFO Please see also https://aquasecurity.github.io/trivy/v0.52/docs/scanner/secret/#recommendation for faster secret detection 2024-07-01T09:50:24+09:00 INFO Detected OS family="debian" version="12.5" 2024-07-01T09:50:24+09:00 INFO [debian] Detecting vulnerabilities... os_version="12" pkg_num=3 2024-07-01T09:50:24+09:00 INFO Number of language-specific files num=1 2024-07-01T09:50:24+09:00 INFO [gobinary] Detecting vulnerabilities... masap20220915/sonobuoy:amd64-v0.57 (debian 12.5) Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0) sonobuoy (gobinary) Total: 9 (UNKNOWN: 0, LOW: 0, MEDIUM: 7, HIGH: 1, CRITICAL: 1) ┌─────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────┬──────────────────────────────────────────────────────────────┐ │ Library │ Vulnerability │ Severity │ Status │ Installed Version │ Fixed Version │ Title │ ├─────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────┼──────────────────────────────────────────────────────────────┤ │ stdlib │ CVE-2024-24790 │ CRITICAL │ fixed │ 1.21.4 │ 1.21.11, 1.22.4 │ golang: net/netip: Unexpected behavior from Is methods for │ │ │ │ │ │ │ │ IPv4-mapped IPv6 addresses │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24790 │ │ ├────────────────┼──────────┤ │ ├─────────────────┼──────────────────────────────────────────────────────────────┤ │ │ CVE-2023-45288 │ HIGH │ │ │ 1.21.9, 1.22.2 │ golang: net/http, x/net/http2: unlimited number of │ │ │ │ │ │ │ │ CONTINUATION frames causes DoS │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2023-45288 │ │ ├────────────────┼──────────┤ │ ├─────────────────┼──────────────────────────────────────────────────────────────┤ │ │ CVE-2023-39326 │ MEDIUM │ │ │ 1.20.12, 1.21.5 │ golang: net/http/internal: Denial of Service (DoS) via │ │ │ │ │ │ │ │ Resource Consumption via HTTP requests... │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2023-39326 │ │ ├────────────────┤ │ │ ├─────────────────┼──────────────────────────────────────────────────────────────┤ │ │ CVE-2023-45289 │ │ │ │ 1.21.8, 1.22.1 │ golang: net/http/cookiejar: incorrect forwarding of │ │ │ │ │ │ │ │ sensitive headers and cookies on HTTP redirect... │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2023-45289 │ │ ├────────────────┤ │ │ │ ├──────────────────────────────────────────────────────────────┤ │ │ CVE-2023-45290 │ │ │ │ │ golang: net/http: memory exhaustion in │ │ │ │ │ │ │ │ Request.ParseMultipartForm │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2023-45290 │ │ ├────────────────┤ │ │ │ ├──────────────────────────────────────────────────────────────┤ │ │ CVE-2024-24783 │ │ │ │ │ golang: crypto/x509: Verify panics on certificates with an │ │ │ │ │ │ │ │ unknown public key algorithm... │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24783 │ │ ├────────────────┤ │ │ │ ├──────────────────────────────────────────────────────────────┤ │ │ CVE-2024-24784 │ │ │ │ │ golang: net/mail: comments in display names are incorrectly │ │ │ │ │ │ │ │ handled │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24784 │ │ ├────────────────┤ │ │ │ ├──────────────────────────────────────────────────────────────┤ │ │ CVE-2024-24785 │ │ │ │ │ golang: html/template: errors returned from MarshalJSON │ │ │ │ │ │ │ │ methods may break template escaping │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24785 │ │ ├────────────────┤ │ │ ├─────────────────┼──────────────────────────────────────────────────────────────┤ │ │ CVE-2024-24789 │ │ │ │ 1.21.11, 1.22.4 │ golang: archive/zip: Incorrect handling of certain ZIP files │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24789 │ └─────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────┴──────────────────────────────────────────────────────────────┘ Signed-off-by: Masashi Honma <masashi.honma@gmail.com> * Fix Windows build ERROR: failed to solve: failed to compute cache key: mount callback failed on /tmp/containerd-mount1917080101: link /tmp/containerd-mount1917080101/Windows/INF/basicrender.inf /tmp/containerd-mount1917080101/Windows/System32/DriverStore/FileRepository/basicrender.inf_amd64_efdc64af60c69a6d/basicrender.inf: no such file or directory Error: Process completed with exit code 1. According to [1], we need to use ltsc2022 as a tag. [1] microsoft/Windows-Containers#493 Signed-off-by: Masashi Honma <masashi.honma@gmail.com> * Add support for injecting tolerations to sonobuoy pod Resolves #1973. We can inject some tolerations to sonobuoy aggregator pod by adding trailing description into sonobuoy config json. { "AggregatorTolerations": [ { "effect": "NoSchedule", "key": "key1", "operator": "Equal", "value": "value1" }, { "effect": "NoSchedule", "key": "key2", "operator": "Equal", "value": "value2" } ] } Signed-off-by: Masashi Honma <masashi.honma@gmail.com> * Bump golang version for build to 1.21.12 To fix trailing warning. Total: 1 (MEDIUM: 1, HIGH: 0, CRITICAL: 0) ┌─────────┬────────────────┬──────────┬────────┬───────────────────┬─────────────────┬──────────────────────────────────────────────────────────┐ │ Library │ Vulnerability │ Severity │ Status │ Installed Version │ Fixed Version │ Title │ ├─────────┼────────────────┼──────────┼────────┼───────────────────┼─────────────────┼──────────────────────────────────────────────────────────┤ │ stdlib │ CVE-2024-24791 │ MEDIUM │ fixed │ 1.21.11 │ 1.21.12, 1.22.5 │ net/http: Denial of service due to improper 100-continue │ │ │ │ │ │ │ │ handling in net/http │ │ │ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2024-24791 │ └─────────┴────────────────┴──────────┴────────┴───────────────────┴─────────────────┴──────────────────────────────────────────────────────────┘ Signed-off-by: Masashi Honma <masashi.honma@gmail.com> --------- Signed-off-by: Masashi Honma <masashi.honma@gmail.com>

markmandel added bug Something isn't working triage New and needs attention labels May 14, 2024

lacroixthomas mentioned this issue May 15, 2024

Generate grpc for nodejs from alpha to beta googleforgames/agones#3825

Merged

zmerlynn mentioned this issue May 15, 2024

Pin ltsc2019 to older SHA googleforgames/agones#3829

Merged

akarshm self-assigned this May 15, 2024

rbtr mentioned this issue May 15, 2024

fix: pin Windows base images microsoft/retina#379

Merged

7 tasks

rbtr mentioned this issue May 16, 2024

fix: pin Windows images Azure/azure-container-networking#2742

Merged

4 tasks

ntrappe-msft removed the triage New and needs attention label May 21, 2024

andyzhangx mentioned this issue May 22, 2024

fix: windows image 1809 build failure kubernetes-csi/csi-driver-smb#785

Merged

4 tasks

Vlatombe mentioned this issue May 30, 2024

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

Closed

dduportal added a commit to dduportal/docker-agent that referenced this issue May 30, 2024

hotfix(Windows Server Core LTSC2019) pin 2019 images to April version…

d02700d

… until microsoft/Windows-Containers#493 is fixed Signed-off-by: Damien Duportal <damien.duportal@gmail.com>

dduportal mentioned this issue May 30, 2024

hotfix(Windows Server Core LTSC2019) pin 2019 images to April version jenkinsci/docker-agent#816

Merged

dduportal added a commit to dduportal/docker-agent that referenced this issue May 30, 2024

hotfix(Windows Server Core LTSC2019) pin 2019 images to April version…

43fc058

… until microsoft/Windows-Containers#493 is fixed Signed-off-by: Damien Duportal <damien.duportal@gmail.com>

jsafrane mentioned this issue May 31, 2024

Need fix for CVE-2023-45288 kubernetes-csi/livenessprobe#261

Closed

carlory mentioned this issue Jun 3, 2024

bump image versions kubernetes-csi/csi-driver-host-path#528

Merged

This was referenced Jun 4, 2024

Cannot pull registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0 kubernetes-csi/node-driver-registrar#415

Closed

livenessproble 2.13.0 image pull not working kubernetes-csi/livenessprobe#273

Closed

profnandaa changed the title ~~COPY on ltsc2019 fails: "mount callback failed"~~ FROM/layer-extraction on ltsc2019 fails: link operation for Windows/INF/basicrender.inf on cross-platform building from Linux Jun 8, 2024

ashutosji mentioned this issue Jun 17, 2024

this will resolve From/layer extraction issue on ltsc2019 in examples googleforgames/agones#3873

Merged

lemeurherve mentioned this issue Jun 26, 2024

fix: pin windowsservercore-ltsc2019 to April 2024 release jenkinsci/docker-ssh-agent#433

Merged

6 tasks

matej-g mentioned this issue Jul 5, 2024

Work around issue for Windows 2019 image coralogix/telemetry-shippers#427

Merged

3 tasks

This was referenced Jul 10, 2024

Revert "hotfix(Windows Server Core LTSC2019) pin 2019 images to April version" jenkinsci/docker-agent#833

Merged

Revert "fix: pin windowsservercore-ltsc2019 to April 2024 release" jenkinsci/docker-ssh-agent#435

Merged

markmandel mentioned this issue Jul 10, 2024

Revert windows ltsc2019 SHA usage. googleforgames/agones#3901

Closed

profnandaa closed this as completed Jul 10, 2024

profnandaa reopened this Jul 12, 2024

profnandaa self-assigned this Jul 12, 2024

akarshm closed this as completed Jul 16, 2024

AbhilashaSGupta mentioned this issue Jul 19, 2024

livenessprobe and csi-node-driver-registrar image versions invalid in gcr overlay for v1.32.0 kubernetes-sigs/aws-ebs-csi-driver#2090

Closed

profnandaa mentioned this issue Oct 23, 2024

WCOW: support for setx, installers vs. ENV, a discussion moby/buildkit#5445

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FROM/layer-extraction on ltsc2019 fails: link operation for `Windows/INF/basicrender.inf` on cross-platform building from Linux #493

FROM/layer-extraction on ltsc2019 fails: link operation for `Windows/INF/basicrender.inf` on cross-platform building from Linux #493

markmandel commented May 14, 2024 •

edited

Loading

markmandel commented May 15, 2024

jsturtevant commented May 15, 2024

markmandel commented May 15, 2024

markmandel commented May 15, 2024

claudiubelu commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

profnandaa commented May 18, 2024

jsafrane commented Jun 5, 2024

profnandaa commented Jun 5, 2024 •

edited

Loading

andriisoldatenko commented Jun 25, 2024

akarshm commented Jul 10, 2024

profnandaa commented Jul 10, 2024

jsafrane commented Jul 11, 2024

lemeurherve commented Jul 11, 2024

jsafrane commented Jul 11, 2024

lemeurherve commented Jul 11, 2024 •

edited

Loading

jsafrane commented Jul 12, 2024

profnandaa commented Jul 12, 2024

jsafrane commented Jul 16, 2024

akarshm commented Jul 16, 2024

FROM/layer-extraction on ltsc2019 fails: link operation for Windows/INF/basicrender.inf on cross-platform building from Linux #493

FROM/layer-extraction on ltsc2019 fails: link operation for Windows/INF/basicrender.inf on cross-platform building from Linux #493

Comments

markmandel commented May 14, 2024 • edited Loading

markmandel commented May 15, 2024

jsturtevant commented May 15, 2024

markmandel commented May 15, 2024

markmandel commented May 15, 2024

claudiubelu commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

jsturtevant commented May 15, 2024

profnandaa commented May 18, 2024

jsafrane commented Jun 5, 2024

profnandaa commented Jun 5, 2024 • edited Loading

andriisoldatenko commented Jun 25, 2024

akarshm commented Jul 10, 2024

profnandaa commented Jul 10, 2024

jsafrane commented Jul 11, 2024

lemeurherve commented Jul 11, 2024

jsafrane commented Jul 11, 2024

lemeurherve commented Jul 11, 2024 • edited Loading

jsafrane commented Jul 12, 2024

profnandaa commented Jul 12, 2024

jsafrane commented Jul 16, 2024

akarshm commented Jul 16, 2024

FROM/layer-extraction on ltsc2019 fails: link operation for `Windows/INF/basicrender.inf` on cross-platform building from Linux #493

FROM/layer-extraction on ltsc2019 fails: link operation for `Windows/INF/basicrender.inf` on cross-platform building from Linux #493

markmandel commented May 14, 2024 •

edited

Loading

profnandaa commented Jun 5, 2024 •

edited

Loading

lemeurherve commented Jul 11, 2024 •

edited

Loading