-
Notifications
You must be signed in to change notification settings - Fork 80
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
panic: required envvar is unset (ROLLBAR_TOKEN) #7
Comments
@vielmetti , |
@vielmetti @parauliya Considering the scenario where a user may not want to use Docker for the whole provisioned setup, I think it would be nice to have a list of all the environment variables. We can have a list of environment variables required for each application to be ready, in the README. And, it would be nice if we can briefly mention what each is required for. |
I ran into this too when testing this morning. Maybe this requirement changed after the README was written? I'd suggest giving a sample that works in the README, even if the context for the env-var choices are written up somewhere else. |
@parauliya the documentation doesn't mention a Docker container, so my understanding from the README is that it should run outside, otherwise the README should prefix the instructions with @nathangoulding do you see a path for usage inside and outside of the container, or should users only use compose? |
I tried copying the instructions from https://github.com/tinkerbell/boots/blob/9d6cded511d1e7678ec601a29aac4137f25ecb5a/installers/rancher/main_test.go, but got as far as:
|
@alexellis The puzzling thing to me is the information about what should be used as the "facility code" - that appears in the current code to resolve to a hard-coded lookup to a |
Perhaps we are now going outside of the happy path? |
We should remove this restriction. |
Closing this as the original issue is no longer present ( Please open additional issues and refer back to this issue if other problems expressed in this thread need to be resolved. |
Successful build on Ubuntu 18.04 for aarch64 under WSL, but when I follow the instructions in the README I get this:
The text was updated successfully, but these errors were encountered: