Skip to content

docker: trying to download cluster-template-docker.yaml: 404 #12015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sebastian-philipp opened this issue Mar 24, 2025 · 4 comments
Closed

docker: trying to download cluster-template-docker.yaml: 404 #12015

sebastian-philipp opened this issue Mar 24, 2025 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@sebastian-philipp
Copy link

What steps did you take and what happened?

$ clusterctl init --infrastructure docker

Fetching providers
Installing cert-manager version="v1.16.3"
Waiting for cert-manager to be available...
Installing provider="cluster-api" version="v1.9.6" targetNamespace="capi-system"
Installing provider="bootstrap-kubeadm" version="v1.9.6" targetNamespace="capi-kubeadm-bootstrap-system"
Installing provider="control-plane-kubeadm" version="v1.9.6" targetNamespace="capi-kubeadm-control-plane-system"
Installing provider="infrastructure-docker" version="v1.9.6" targetNamespace="capd-system"

Your management cluster has been initialized successfully!

You can now create your first workload cluster by running the following:

  clusterctl generate cluster [name] --kubernetes-version [version] | kubectl apply -f -

and

$  clusterctl -v 100  generate cluster capi-quickstart --flavor docker   --kubernetes-version v1.32.0
No default config file available
Potential override file searchFile="/Users/sebastian/Library/Application Support/cluster-api/overrides/infrastructure-docker/v1.9.6/cluster-template-docker.yaml" provider="infrastructure-docker" version="v1.9.6"
Fetching file="cluster-template-docker.yaml" provider="docker" type="InfrastructureProvider" version="v1.9.6"
error using httpGet to get file from GitHub releases, falling back to github client: 404 Not Found owner="kubernetes-sigs" repository="cluster-api" version="v1.9.6" path="cluster-template-docker.yaml"
Error: failed to read "cluster-template-docker.yaml" from provider's repository "infrastructure-docker": failed to download files from GitHub release v1.9.6: failed to get file "cluster-template-docker.yaml" from "v1.9.6" release
sigs.k8s.io/cluster-api/cmd/clusterctl/client/repository.(*templateClient).Get
	sigs.k8s.io/cluster-api/cmd/clusterctl/client/repository/template_client.go:96
sigs.k8s.io/cluster-api/cmd/clusterctl/client.(*clusterctlClient).getTemplateFromRepository
	sigs.k8s.io/cluster-api/cmd/clusterctl/client/config.go:340
sigs.k8s.io/cluster-api/cmd/clusterctl/client.(*clusterctlClient).GetClusterTemplate
	sigs.k8s.io/cluster-api/cmd/clusterctl/client/config.go:257
sigs.k8s.io/cluster-api/cmd/clusterctl/cmd.runGenerateClusterTemplate
	sigs.k8s.io/cluster-api/cmd/clusterctl/cmd/generate_cluster.go:194
sigs.k8s.io/cluster-api/cmd/clusterctl/cmd.init.func8
	sigs.k8s.io/cluster-api/cmd/clusterctl/cmd/generate_cluster.go:103
github.com/spf13/cobra.(*Command).execute
	github.com/spf13/cobra@v1.8.1/command.go:985
github.com/spf13/cobra.(*Command).ExecuteC
	github.com/spf13/cobra@v1.8.1/command.go:1117
github.com/spf13/cobra.(*Command).Execute
	github.com/spf13/cobra@v1.8.1/command.go:1041
sigs.k8s.io/cluster-api/cmd/clusterctl/cmd.Execute
	sigs.k8s.io/cluster-api/cmd/clusterctl/cmd/root.go:113
main.main
	sigs.k8s.io/cluster-api/cmd/clusterctl/main.go:27
runtime.main
	runtime/proc.go:271
runtime.goexit
	runtime/asm_arm64.s:1222

I'm still trying to figure out what is going on here, but please, can you at least log the url you're trying to download?

What did you expect to happen?

I got a 404

Cluster API version

clusterctl version: &version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.5", GitCommit:"068c0f3c8ed3a7e382952f8ae68b648aee240a60", GitTreeState:"clean", BuildDate:"2025-02-18T19:11:43Z", GoVersion:"go1.22.12", Compiler:"gc", Platform:"darwin/arm64"}

Kubernetes version

Client Version: v1.32.0
Kustomize Version: v5.5.0
Server Version: v1.32.0

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 24, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sbueringer
Copy link
Member

sbueringer commented Mar 24, 2025

You have to use flavor "development"

@chrischdi chrischdi added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Mar 25, 2025
@k8s-ci-robot k8s-ci-robot removed the needs-priority Indicates an issue lacks a `priority/foo` label and requires one. label Mar 25, 2025
@chrischdi
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@chrischdi: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

4 participants