kubernetes-sigs/image-builder

make docker-build giving issue - invalid reference format

shruthihub opened this issue · 5 comments

shruthihub commented

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
on git clone and in images/capi directory , i ran make docker-build
but i got a error that says :
invalid argument "gcr.io//cluster-node-image-builder-amd64:dev" for "-t, --tag" flag: invalid reference format

What did you expect to happen:
docker image creation has to happen

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

Project (Image Builder for Cluster API, kube-deploy/imagebuilder, konfigadm):

Additional info for Image Builder for Cluster API related issues:

  • OS (e.g. from /etc/os-release, or cmd /c ver):
  • Packer Version:
  • Packer Provider:
  • Ansible Version:
  • Cluster-api version (if using):
  • Kubernetes version: (use kubectl version):

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

mohitsharma-in commented

Seems to be like you might not be able to run REGISTRY ?= gcr.io/$(shell gcloud config get-value project) specifically shell gcloud section which might be resulting in the error.

Can you please try Passing REGISTRY= make docker-build

k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

LittleChimera commented

Seems to be like you might not be able to run REGISTRY ?= gcr.io/$(shell gcloud config get-value project) specifically shell gcloud section which might be resulting in the error.

Can you please try Passing REGISTRY= make docker-build

Something similar works:

REGISTRY=docker.io/library make docker-build
k8s-triage-robot commented

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

AverageMarcus commented

Sorry for the delay, I've opened a PR to fix this so you don't need to override the registry if not needed: #1199