You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am some problem to get sbom-action working on windows image.
By same workflow on Linux images everything goes well.
Here is what I've done sofar:
built the windows image named "eclipse-temurin:8u332-b09-jre-nanoserver-ltsc2022" with Dockerfile from source repo.
done "docker image ls", to confirm the image is successfully created by GH action
ran anchore/sbom-action got error: * failed to construct source from user input "eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022": could not fetch image "eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022": unable to use OciRegistry source: failed to get image from registry: no child with platform linux/amd64 in index eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022
Since I do not have a windows to reproduce it locally, my guess is, even it is on
After setting up WSL, syft consider this is a Linux OS, that's why it does not use the images built by previous step nor can pull down image with the same name from public registry to match "platform linux/amd64"
I am using the latest sbom-action, which has v0.53.4 syft
The text was updated successfully, but these errors were encountered:
Hi,
I am some problem to get sbom-action working on windows image.
By same workflow on Linux images everything goes well.
Here is what I've done sofar:
anchore/sbom-action
got error:* failed to construct source from user input "eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022": could not fetch image "eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022": unable to use OciRegistry source: failed to get image from registry: no child with platform linux/amd64 in index eclipse-temurin:8u332-b09-jre-windowsservercore-ltsc2022
Since I do not have a windows to reproduce it locally, my guess is, even it is on
After setting up WSL, syft consider this is a Linux OS, that's why it does not use the images built by previous step nor can pull down image with the same name from public registry to match "platform linux/amd64"
I am using the latest
sbom-action
, which hasv0.53.4 syft
The text was updated successfully, but these errors were encountered: