.

perhaps the repo from which you're pulling has some sort of access control, and the docker client recognizes that. I'm just guessing; I don't recall ever seeing this myself.

no treally

Normally

docker logout

would be the solution to this if you're pulling public images.

can you explain a bit on why it's asking for the credential

Because you're logged in.

so it's better to

docker logout

than to provide keychain access?

When you're logged in, it allows you to access your private images. The token is stored in your keychain.

i'll be frank the only reason im askin gall this is because orbstack is closed source

Logging in may allow you to bypass Docker Hub's pull limits as well

and i dont know if it can access the credential if i allow access

Again, this has nothing to do with Orbstack

ohk

You'll get entirely the same behavior with any docker provider, including colima or Docker Desktop

hmm i was just wondering if orbstack could possibly ship a modified version of

docker

and could access the credentials 🙂

You can just use the one from homebrew

with orbstack?

Yes

would u recommend that? or should i just give access

It doesn't matter

This also depends on your docker configuration file

Detail about credential stores is at https://docs.docker.com/reference/cli/docker/login/

As mentioned by rfay, this has nothing to do directly with Orbstack

It's your config.json that determines the behavior. And what it says there is "automatically saved to native keychain" which is what you're seeing

yes and orbstack docs say it saves to a different credentail store (desktop) which is not true

osxkeychain is the native keychain. You can configure this as you wish in your .docker/config.json

You can use osxkeychain for docker, podman, orbstack, etc

i understand that . what im saying is that the orbstack docs wrongly claim docker desktop uses a different keychain

Why don't you explore the keychain to see what's happening? Are you aware that you're complaining to just a couple of random users? Both could use different keys in the same keychain.

This really doesn't matter either way, what is in your docker configuration file

sorry i think there's a misunderstanding

So everything is working then for you to pull?

yes

If you wanted to improve the docs, you'd open an issue in the issue queue. But I'm not sure you're correct. I think the difference is probably "which key in keychain" than "which keychain"

i don't know why you sound like you're angry . i definitely thought of opening an issue, in fact even looked up the github org if the docs were open source and i could contribute directly . just mentioned here because we were talking on the same topic. i don't hv any ill intentions and im loving orbstack . thank you 🙂

I think the confusion here is that docker doesn't use the keychain the same way as orbstack