Stereoscope cannot inspect images in Docker Desktop about stereoscope

[timpur]

I can confirm that this bug was introduced in v0.61.0
v0.60.0 workes as normal

New version of grype is available: 0.61.1 (currently running: 0.61.0)
 ⠼ Pulling image           

1 error occurred:
        * failed to catalog: could not fetch image "

New version of grype is available: 0.61.1 (currently running: 0.60.0)
 ✔ Loaded image            
 ✔ Parsed image            
 ✔ Cataloged packages      [214 packages]
 ✔ Scanning image...       [10 vulnerabilities]

[Nicu-Ducal]

Nevermind, apparently if you have Docker Desktop and docker service on UNIX and you have your images on Docker Desktop, it's not looking for them on docker desktop. I've turned off Docker Desktop and moved my images to docker service and now it's ok. You can close it or maybe investigate how to look up for Docker Desktop images also

[purujitgoyal]

Hey @tgerla, it's working for me now. I'm on v0.66.0.

[Nicu-Ducal]

I have tried it with v0.60.0 and it still gives me the same error.

╰─ grype custom-rabbit                                                                                                    
 ✔ Vulnerability DB        [no update available]
New version of grype is available: 0.61.1 (currently running: 0.60.0)
 ⠴ Pulling image           
1 error occurred:
	* failed to catalog: could not fetch image "custom-rabbit": unable to use DockerDaemon source: pull failed: Error response from daemon: pull access denied for custom-rabbit, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I have restarted my machine and docker as well, same thing :(

[tgerla]

Hi @Nicu-Ducal, thanks for the report and the updates. We think it has to do with a new feature in Docker Desktop: specifically, being able to change which socket file is used to communicate with Docker Desktop. We will need to do some investigation to figure out what exactly is going on.

As a possible workaround can you go to your Docker Desktop settings and select Advanced, and select "Enable default Docker socket"?

[purujitgoyal]

Facing the same issue. Upgraded to v0.61.0 from v0.59.0 and started having this issue.

@tgerla the workaround is not working as well.

[Nicu-Ducal]

As a possible workaround can you go to your Docker Desktop settings and select Advanced, and select "Enable default Docker socket"?

I think I have an older version of Docker Desktop, which doesn't even have this specific setting :( I can Update if you desire

[tgerla]

Possibly related to: anchore/grype#1314

[spiffcs]

If there is an issue with Desktop Vs Service then it might have to do with how they treat the socket in the latest release:
https://github.com/anchore/syft/blob/main/DEVELOPING.md#docker-settings-for-getting-started

Check out these docs we just added which show how to setup the context and allow the default docker socket to be used - If there is anything different on linux as far as the desktop settings let me know and I can update the docs!

[tgerla]

HI @purujitgoyal and @Nicu-Ducal, we have made some updates to the way that we communicate with Docker Desktop in Syft 0.86 (included in the latest version of Grype) -- can you upgrade and see if you are still seeing problems?

[Nicu-Ducal]

Hi @tgerla! I'll give it a try maybe this weekend or on Tuesday, thanks for the notice!

[tgerla]

Hi @Nicu-Ducal, just checking to see if you are still having problems with this...happy to help out if you are still seeing issues!

[Nicu-Ducal]

Hey @tgerla! Sorry for ghosting you, just had a lot of work lately and didn't really had time to check it. I've tried now and it still seems to now see the images that were created by Docker Desktop Daemon :( It's okay though, because I've stopped using it and I'm just using the CLI daemon now and it works fine with it.

P.S. It raises the same error as previously

[tgerla]

Thanks @purujitgoyal and @Nicu-Ducal for your responses. Nicu, I'll go ahead and close this issue but if you would ever like us to revisit it with you, please re-open this or find us on Slack and we will be happy to help!

[Nicu-Ducal]

Sure thing, thank you @tgerla for your help and input!