portainer/portainer · error

cannot use ToStdout with OutFile

Error message

cannot use ToStdout with OutFile

What it means

Error "cannot use ToStdout with OutFile" thrown in portainer/portainer.

Source

Thrown at pkg/libkompose/convert.go:84

		return nil, fmt.Errorf("invalid volumes %q: must be one of: persistentVolumeClaim, emptyDir, hostPath, configMap", volumes)
	}

	yamlIndent := opts.YAMLIndent
	if yamlIndent == 0 {
		yamlIndent = 2
	} else if yamlIndent < 0 {
		return nil, fmt.Errorf("invalid yamlIndent %d: must be a positive integer", yamlIndent)
	}

	if !validControllers[opts.Controller] {
		return nil, fmt.Errorf("invalid controller %q: must be one of: deployment, daemonSet, replicationController, deploymentConfig", opts.Controller)
	}

	if opts.ToStdout && opts.CreateChart {
		return nil, errors.New("cannot use ToStdout with CreateChart")
	}
	if opts.ToStdout && opts.OutFile != "" {
		return nil, errors.New("cannot use ToStdout with OutFile")
	}

	return &kobject.ConvertOptions{
		OutFile:                 opts.OutFile,
		CreateChart:             opts.CreateChart,
		GenerateYaml:            true,
		GenerateJSON:            false,
		ToStdout:                opts.ToStdout,
		Namespace:               opts.Namespace,
		Provider:                provider,
		Controller:              opts.Controller,
		Replicas:                replicas,
		Volumes:                 volumes,
		PVCRequestSize:          opts.PVCRequestSize,
		GenerateNetworkPolicies: opts.GenerateNetworkPolicies,
		YAMLIndent:              yamlIndent,
		Build:                   "none",
		WithKomposeAnnotation:   false,

View on GitHub (pinned to 17e74456ff)

When it happens

Trigger: Thrown at pkg/libkompose/convert.go:84 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of portainer/portainer@17e74456ff (2026-08-26). Data as JSON: /api/errors/b11df5478a99794e. Report an issue: GitHub.