Pulling features from ghcr hanges without access token in creds store

Hi,

It took me forever to figure out why my "open in dev container" commands were hanging every time it needed to pull an image from a repository to use a feature, usually ghcr from what i noticed. Weirdly enough, running `docker-credential-desktop get` would hang in both Powershell and WSL. and I noticed this was the step that the boot sequence would usually hang on. I got around this by running `docker login https://ghcro.io --username ` and using a classic personal access token. now the images seem to be pulling fine, but there was no indication this was causing the issue, and took a lot of digging around and figuring out what was happening in the credsStore config, etc.

Not sure if this is a Windows/WSL issue only but it seems like OSX users were running into a lot of credentials issues in open issues during my research.

I hope this is helpful feedback.

Commencez par reproduire la récupération de l’image de fonctionnalité du conteneur de développement depuis ghcr dans PowerShell et WSL, puis comparez la séquence de démarrage avec `docker-credential-desktop get` et la configuration `credsStore`. C’est terminé lorsque la récupération ne se bloque plus ou signale clairement le problème d’identifiants, avec un comportement vérifié par rapport au contournement `docker login` signalé.

Rédigé par le modèle d'indexation à partir du texte de l'issue.