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

Improve installation instructions #132

Open
zasgar opened this issue Jan 20, 2022 · 1 comment
Open

Improve installation instructions #132

zasgar opened this issue Jan 20, 2022 · 1 comment

Comments

@zasgar
Copy link
Member

zasgar commented Jan 20, 2022

Reported by @daz:

Hey folks! Have been intrigued by Pixie for some time and, after listening to your developers interesting discussion on Kubelist podcast today, was prompted to try. I'm making progress but I think some improvements could be made to the install instructions. I'm always loathe to use (bash) installers on Linux but, the Docker solution has flaws and the install the binary correctly suggests checking the binary's hash but does not provide a convenient link to determine the hash. I'm using: https://docs.pixielabs.ai/installing-pixie/install-guides/ and https://docs.pixielabs.ai/installing-pixie/install-schemes/cli/
Docker
I'm using Podman but alias px="podman run --interactive --rm --name=pixie --volume=${HOME}/.pixie:/root/.pixie --volume=${HOME}/.kube/config:/root/.kube/config pixielabs/px" even with the volume for the cluster config, this requires a prior mkdir ${HOME}/.pixie step and fails because it's unable to find kubectl for px deploy.
Binary
Suggests (good practice!) # Check the signature matches. but it's unclear where the hash is to be found!?
The binary referenced in the page is evidently for MacOS (default?) cli_darwin_amd64 but, I'm using Linux and guessed (correctly) that I want cli_linux_amd64
Step #2 is "Deploy Pixie" using px deploy but this fails requiring that the user first px auth login
This isn't successful (yet) for me with:
Failed to perform browser-based auth. Will try manual autho error=missing code, assuming auth failed
But, on my second attempt using login?local_mode=true I get:
Failed to login error="rpc error: code = Internal desc = server closed the stream without sending trailers"
Third time lucky... I noticed the prompt to update to "0.7.2" having just installed using the Pixie installation page (!) and this appears to have resolved my issue. (edited)

docs.pixielabs.ai
Installing Pixie | Install Guide
Getting started guide to setup Pixie

docs.pixielabs.ai
Install | Install Schemes (optional) | CLI
How to install Pixie via CLI

@DazWilkin
Copy link

Thanks for filing this for me @zasgar

I'm happy to help debug|improve the instructions too.

I like the fact that your docs include the possibility of running px from a container; this would be one (!) of my preferences too. If the only omission is kubectl, this should be relatively straightforward to resolve. I gave up at this point today and switched to the binary release.

For other folks who (don't want to run from a container and) use (Ubuntu) Snaps, it would be great to have Pixie provide a Snap too. Although not as prevalent, this should require minimal effort.

Great technology but, like me, other users may have short attention spans and could be easily discouraged from hurdles getting-going.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants