Leonard Sheng Sheng Lee
Leonard Sheng Sheng Lee
> This worked for me, thanks @true-real-michael ! > > Keybinding I configured: > > ``` > keybinds { > normal { > unbind "Alt f" > bind "Alt F"...
> @sheeeng is this image `cr.l5d.io/linkerd/proxy:stable-2.14.10` pulled from private registry? if so how are you setting secrets ? Thank you for the tip. I will check on it. Get back...
```yaml proxy: image: name: ghcr.io/linkerd/proxy ``` I have tried to change the default container image name to use `ghcr.io` prefix, but to no avail. ```json {"level":"error","ts":"2024-05-22T08:06:58Z","logger":"reconciler.scan job","msg":"Scan job container","job":"trivy/scan-vulnerabilityreport-564746fb59","container":"linkerd-proxy","status.reason":"Error","status.message":"2024-05-22T08:06:55.383Z\t\u001b[31mFATAL\u001b[0m\timage scan...
> @sheeeng if it is private then yes if public no According to [Using A Private Docker Repository | Linkerd](https://linkerd.io/2.15/tasks/using-a-private-docker-repository/), all of the Linkerd images are publicly available at the...
> @sheeeng it works for other public images but for this one it fails ? Yes, it works for other public images. ```console $ kubectl get vulnerabilityreports.aquasecurity.github.io --all-namespaces --output json...
> I think the issue relate to settings, you mention that you tried to change the image name from `cr.l5d.io/linkerd/proxy:stable-2.14.10` to `ghcr.io/linkerd/proxy` something in the way you changed it, as...
I was able to pull container images from both `cr.l5d.io` and `ghcr.io` without authentication successfully. ```shell podman pull cr.l5d.io/linkerd/controller:stable-2.14.10 podman pull ghcr.io/linkerd/proxy:stable-2.14.10 ``` It can generate `VulnerabilityReport` inside a minimal...
I managed to reproduce this issue using Linkerd with CNI plugin on local Podman Desktop using following steps. The previous experiment that produces no error was using plain Linkerd only....
Same stacktrace is found on https://github.com/aquasecurity/trivy-operator/issues/2101#issue-2317860263 too.
> @sheeeng what is the status of this issue have you found workaround > @sheeeng the errors issue fixed by `trivy-operator v0.21.3` feel free to re-open if you think issue...