Verbose log messages relating to config.json

[BenHall]

With the recent v1.0.0 release, if a config.json doesn't exist then the user is shown a lot of log messages that can be overwhelming.

$   Downloading Kubernetes v1.14.0 images in the background ...
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
>   Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous
2019/03/27 17:12:49 Unable to read "/root/.docker/config.json": open /root/.docker/config.json: no suchfile or directory
2019/03/27 17:12:49 No matching credentials were found, falling back on anonymous

[BenHall]

Likewise, if it's not a valid json file

2019/03/27 17:21:10 Unable to parse "/root/.docker/config.json": unexpected end of JSON input
2019/03/27 17:21:10 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:10 Unable to parse "/root/.docker/config.json": unexpected end of JSON input
2019/03/27 17:21:10 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:10 Unable to parse "/root/.docker/config.json": unexpected end of JSON input
2019/03/27 17:21:10 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:10 Unable to parse "/root/.docker/config.json": unexpected end of JSON input
2019/03/27 17:21:10 No matching credentials were found, falling back on anonymous

If the file contains valid json but no credentials then they see:

2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous
2019/03/27 17:21:44 No matching credentials were found, falling back on anonymous

[afbjorklund]

Was this when using the none driver as root, or when does it happen ?

[BenHall]

@afbjorklund Yep

Environment @ https://beta.katacoda.com/courses/kubernetes/launch-single-node-cluster

[tstromberg]

Thanks for bringing this up @BenHall.

I hit this issue with macOS (no Docker installed) as well. I'd love to see it fixed.

[afbjorklund]

It's yet another github.com/google/go-containerregistry feature. It logs all 3 of these things:

pkg/authn/keychain.go: log.Printf("Unable to read %q: %v", file, err)

pkg/authn/keychain.go: log.Printf("Unable to parse %q: %v", file, err)

pkg/v1/remote/options.go: log.Println("No matching credentials were found, falling back on anonymous")

[afbjorklund]

Related to google/go-containerregistry#390

[afbjorklund]

But as long as you have your docker credentials* set up properly, none of this is shown...

• https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Should be fixed (upstream) anyway of course, but that is why I didn't see it myself for instance.

{
	"experimental": "enabled",
	"credsStore": "secretservice"
}

[aseempatni]

I hit the same issue today on Oracle Linux using none driver as root.

[locojuhi]

I've just installed virtualbox, kubectl and minikube... but when I run minikube start it freeze when is downloading the minikube iso

😄 minikube v1.0.0 on linux (amd64)
🤹 Downloading Kubernetes v1.14.0 images in the background ...
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
💿 Downloading Minikube ISO ...
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2019/04/22 22:19:13 No matching credentials were found, falling back on anonymous
2.25 MB / 142.88 MB [>------------------------------------------] 1.57% 9m36s

I haven't found any solution so far... any suggestion?

[Guojunzhou-git]

eh, It occurred to me too, and it's more difficult for me in China because "the Great Network Wall".
so do we have a convenient download way for Chineses?

[tdfacer]

I was attempting to set this up on my Arch Linux machine and found that the minikube package installed from the official community repo resulted in the "No matching credentials were found, falling back on anonymous" error. Instead, I installed the minikube-bin package from the AUR and was successful in getting my local environment set up. Before switching I ran a rm -rf ~/.minikube for good measure (since it wasn't automatically removed by running sudo pacman -Rns minikube).