The screenshot was outdated, configuration is done in each job

There are more docs linked to https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/chapter-docker-build-publish.html

Thanks Carlos!
If this is true, the "Registry credentials" is not working with a private docker registry. The error message is pasted below.

$ docker push ****.io/docker-abc
The push refers to a repository [****]
4f77f877cd62: Preparing
290efca864d1: Preparing
a93e5549dca1: Preparing
0459986018de: Preparing
no basic auth credentials

Follow up with my question, and change the issue title accordingly.
Thanks for helping!

We thought we could use it for our private registry turns out this is not the case. As Jenkins Enterprise customers we would love to be able to specify which registry the credentials are for.

Another issue is that users keep selecting this option with invalid credentials and it breaks builds. Because it writes a docker credentials file to /home/jenkins/.dockercfg with bad credentials. No one can pull from docker.io because we are getting auth errors against docker.io in all the jobs now. Everyone who uses that build slave cant pull images because of one person's misconfiguration ina job. Is there some less persistent way to insert the credentials on a per job basis?