https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
➕ 1
k
How so? I found that 0.7.0 doesn't work on my machine, but we didn't release that in 1.6.0
q
It insists on popping up when i try to do some normal function for which i have no need / interest in giving anyone any credentials. Probably 
docker pull
? -- my solution was 
rm
-- it was an effective solution
k
You could also change the 
credsStore
field in 
~/.docker/config.json
to 
"none"
, but that will store your actual credentials in plain-text base64 in 
~/.docker/plaintext-credentials.config.json
, created with perms 0600. If your machine is secure you could always use that.
q
i could have sworn i'd done that once before
I presume some stupid thing felt it was a good favor to wipe out my preference.
anyway, that doesn't justify the braindead behavior of docker-credential-osxkeychain
if i don't need credentials, it shouldn't waste my time asking me for permission to unlock the os keychain
k
I'm still not sure what happened with https://github.com/docker/docker-credential-helpers/issues/246 -- no answer after 10 days. If I build it on my machine, it works, but if I download the release version it's borken
q
knock on the door first, if it's open, go in, don't first ask "hey, could I have your keys?" before trying to open the door.
k
But if you're switching between RD and DD, DD always sets the 
credsStore
field to 
"docker"
. And when RD starts up, if that field is set to 
"desktop"
it gets set to the platform-specific 
credsStore
, which is the most likely explanation for it bouncing back to 
osxkeychain
q
I believe this computer has never met DD
k
And the go code is mostly a shim around C++ code to call the library, so I haven't figured out the breakage
q
and I certainly haven't used it on computers I control in ages
k
ok
q
(i did uninstall DD from a colleague's computer last week)
k
Strange then, unless you cleared away the 
~/.docker
directory
q
Copy code
jsoref@jsoref-mbp templates % ls -hal ~/.docker
total 32
drwxr-xr-x   14 jsoref  staff   448B Oct 24 14:52 .
drwxr-xr-x+ 378 jsoref  staff    12K Oct 24 14:52 ..
-rw-------    1 jsoref  staff    64B Oct 25  2018 .buildNodeID
-rw-------    1 jsoref  staff   132B Jul 26 18:23 .token_seed
-rw-------    1 jsoref  staff     0B Mar 24  2021 .token_seed.lock
drwxr-xr-x    5 jsoref  staff   160B Dec 17  2020 application-template
drwx------    7 jsoref  staff   224B Jun 29 16:37 buildx
drwxr-xr-x    4 jsoref  staff   128B Oct 13 12:15 cli-plugins
-rw-------    1 jsoref  staff   2.3K Oct 24 14:52 config.json
drwxr-xr-x    4 jsoref  staff   128B Apr  4  2021 contexts
-rw-r--r--@   1 jsoref  staff   147B May 18  2021 daemon.json
drwxr--r--    3 jsoref  staff    96B Aug  6  2021 devenvironments
drwxr-xr-x    3 jsoref  staff    96B Jan 26  2022 run
drwxr-xr-x    3 jsoref  staff    96B Jan 24  2022 scan
given that 
application-template
dates to 2020 and the 
.token_seed.lock
to 2021, that seems unlikely
k
We wrote 
docker-credential-none
to run tests on CI where we don't want random dialog boxes popping up
ok, if you can repro something definitely pls let me know
q
i don't really log every operation i take, that'd run me out of disk space very quickly 😞. As it is, one of my servers ran out of disk space this morning (terrible morning)
but yeah, if I have some insight, I'll shout 🙂
k
I don't mean that
I mean if you see it happen again, and can figure out why, definitely let me know.
We've got QA people here who dig into those sorts of things as their main job
q
For which I'm thankful. Although my last experience w/ a QA team in trying to repro something was abject failure (I got a nice apology from the head of the team) -- I did manage to poison someone else's computer at the vendor, so they're now debugging and it'll be fixed... sigh... heisenbugs are so frustrating
oh, should i try using 0.6.4?
is that likely to be less annoying / provide some interesting experience?
ok, earthly hates me, and I'm pretty sure it's the same problem, although I don't understand the details https://ci.earthly.dev/logs?logId=93c26b2f-80eb-4e42-8e19-52cf4a143d3a
Right, 1.6.1 on 12.6.1 helpfully restored the broken 
none
helper. Replacing it w/ the 
none
helper from 
main
(w/ a working logging pass through) results in things working....
1348 Views
Open in Slack
PreviousNext
Powered by