Skip to content
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

Error Encountered When Using 'kn quickstart minikube' Command with Knative cli #5722

Closed
AugustasV opened this issue Oct 19, 2023 · 8 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter

Comments

@AugustasV
Copy link

Expected Behavior

The quickstart command is expected to work as described in the Knative documentation.

Actual Behavior

When running the docker command mentioned in the Knative documentation, an error is encountered. The error message indicates that the quickstart command is unknown for the kn tool.

Steps to Reproduce the Problem

  1. Run the following command:
    docker run --rm -v "$HOME/.kube/config:/root/.kube/config" gcr.io/knative-releases/knative.dev/client/cmd/kn:latest quickstart minikube
    
  2. Observe the error message: "Error: unknown command 'quickstart' for 'kn'."

Additional Info

Additional context
Knative Quickstart Installation.

Install information:

  • Platform (GKE, IKS, AKS, etc.): Local/Minikube
  • Knative Version: v1.11.1
@AugustasV AugustasV added the kind/bug Categorizes issue or PR as related to a bug. label Oct 19, 2023
@Cali0707
Copy link
Member

@AugustasV did you install the quickstart plugin? Quickstart is a separate dependency which must also be added, on top of the core kn tool

@Cali0707
Copy link
Member

/triage needs-user-input

@knative-prow knative-prow bot added the triage/needs-user-input Issues which are waiting on a response from the reporter label Oct 19, 2023
@AugustasV
Copy link
Author

Yes now I see... but still to add as a plugin somehow didn't worked as expected on my system. I used kn-quickstart minikube
Why those packages can't be installed with go in simple way something like go install https://github.com/knative@latest ?

But Yes my fault, didn't noticed.

@Cali0707
Copy link
Member

cc @dsimansk @rhuss

Any ideas about the above question?

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 19, 2024
@rhuss
Copy link
Contributor

rhuss commented Jan 22, 2024

/remove-lifecycle stale

Sorry, I'm not deep in the quickstart plugin and so I'm not of great help. @psschwei , maybe you have an idea ?

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 22, 2024
@psschwei
Copy link
Contributor

The preferred ways to install have historically been through either brew or downloading the binary from the Github releases page. Using go get/install wasn't really considered when we first came up with the idea of the quickstart plugin.

As to why go install knative.dev/kn-plugin-quickstart doesn't work, here's what happens when trying to run that command:

$ go install knative.dev/kn-plugin-quickstart@latest
go: downloading knative.dev/kn-plugin-quickstart v0.39.1
go: knative.dev/kn-plugin-quickstart@latest: module knative.dev/kn-plugin-quickstart@latest found (v0.39.1), but does not contain package knative.dev/kn-plugin-quickstart

If someone wanted to submit a PR to get go install working, I'd be happy to help get it merged, but it's not something I personally have the bandwidth these days to tackle.

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter
Projects
None yet
Development

No branches or pull requests

4 participants