kubernetes/kops · error

reading Docker config from stdin: %v

Error message

reading Docker config from stdin: %v

What it means

RunCreateSecretDockerConfig reads the Docker config from stdin (path '-') via ConsumeStdin; this wraps that read failing - stdin closed/empty or an I/O error. The secret store client was already built successfully.

Source

Thrown at cmd/kops/create_secret_dockerconfig.go:113

	if err != nil {
		return err
	}

	clientset, err := f.KopsClient()
	if err != nil {
		return err
	}

	secretStore, err := clientset.SecretStore(cluster)
	if err != nil {
		return err
	}

	var data []byte
	if options.DockerConfigPath == "-" {
		data, err = ConsumeStdin()
		if err != nil {
			return fmt.Errorf("reading Docker config from stdin: %v", err)
		}
	} else {
		data, err = os.ReadFile(options.DockerConfigPath)
		if err != nil {
			return fmt.Errorf("reading Docker config %v: %v", options.DockerConfigPath, err)
		}
	}

	var parsedData map[string]interface{}
	err = json.Unmarshal(data, &parsedData)
	if err != nil {
		return fmt.Errorf("unable to parse JSON %v: %v", options.DockerConfigPath, err)
	}

	secret := &fi.Secret{
		Data: data,
	}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Pipe a valid Docker config JSON into the command, e.g. cat config.json | kops create secret dockerconfig -
2. Ensure stdin is not closed or redirected incorrectly
3. Use a file path instead of '-' if not piping

When it happens

Trigger: Thrown at cmd/kops/create_secret_dockerconfig.go:113 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/1adf1e734b283567. Report an issue: GitHub.