sticky-summer-13450
07/23/2022, 9:14 AMpass
.
Having pass
installed completely changes the way docker login
works. It stops all of the (admittedly fairly insecure) auths from .docker/config.json
from working. To use docker login
, and any interaction with registries which relies on docker login
, pass
insists that the user uses gpg
to create a key and reenters their docker login
credentials.
This change was sprung upon me just by installing Rancher Desktop.
For me, this stopped me from working for a while, which delayed a deployment, whilst I looked up all the manuals I needed to learn this new approach.
Maybe pass
could be suggested by Rancher Desktop instead of be depended upon by Rancher Desktop?fast-garage-66093
07/24/2022, 12:16 AMnerdctl
has nothing to talk to. We will ship a none
helper with the next release, that will store credentials in a text file instead: Build a standalone docker-credential-none. by ericpromislow · Pull Request #2372 · rancher-sandbox/rancher-desktopnone
instead of pass
if pass
has not been setup properly; unfortunately that won't make it into the next release anymore 😞sticky-summer-13450
07/24/2022, 11:24 AMpass
was added between 1.3 and 1.4 - on this desktop I only upgraded to 1.4 in the last week or two. But I'll have used it (with docker (moby)) back end for those weeks and did not notice am issue with RD - so I guess RD worked okay with pass
installed but obviously not working, due to gpg
not having any keys.
Anyway - just mentioning it. The need for pass
and gpg
to be configured and working was not something I'd seen mentioned here on Slack, so I thought I'd mention it. Maybe I'm unusual in using RD on Linux, or maybe I'm unusual in not having a GPG identity... 🤷