docs: update common error message in troubleshooting #5973
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: AnaisUrlichs <urlichsanais@gmail.com>
knqyf263
reviewed
Jan 19, 2024
| * remote error: GET https://index.docker.io/v2/ContainerImageName: MANIFEST_UNKNOWN: manifest unknown; unknown tag=0.1 | ||
| ``` | ||
|
|
||
| Trivy is unable to access the container image on the remote registry. If you did not specify a registry, Trivy will use the Docker Container Registry. |
There was a problem hiding this comment.
It means Trivy is unable to find the container image in the following places.
- docker daemon
- containerd
- podman
- remote registry
trivy image --help | grep image-src
--image-src strings image source(s) to use, in priority order (docker,containerd,podman,remote) (default [docker,containerd,podman,remote])
The default registry is Docker Hub.
There was a problem hiding this comment.
so why did it not scan my container image that I just built prior to running the command?
There was a problem hiding this comment.
It depends on your configuration. If your local daemon is not located in the default path, you must specify the path.
$ trivy image -h | grep docker-host
--docker-host string unix domain socket path to use for docker scanning
OR DOCKER_HOST also works.
https://docs.docker.com/engine/reference/commandline/cli/
There was a problem hiding this comment.
Oki, thank you, I will update the description
| ``` | ||
|
|
||
| Trivy is unable to access the container image on the remote registry. If you did not specify a registry, Trivy will use the Docker Container Registry. | ||
| The container image will likely have to be pushed first to the registry. Then, try to pull the same container image from the registry. |
There was a problem hiding this comment.
Trivy can scan local images.
Signed-off-by: chenk <hen.keinan@gmail.com>
Signed-off-by: AnaisUrlichs <urlichsanais@gmail.com>
…asecurity#5929) Signed-off-by: AnaisUrlichs <urlichsanais@gmail.com> Co-authored-by: saso <sasoakira6114@gmail.com>
Signed-off-by: AnaisUrlichs <urlichsanais@gmail.com>
AnaisUrlichs
force-pushed
the
troubleshooting-update
branch
from
59e6fc8
to
46b6d5b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I see several people struggle with this error message