-
Notifications
You must be signed in to change notification settings - Fork 137
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
Why is git a pre-requirement in setup.sh? #172
Comments
Oh we now need to git clone the tink repo? The setup.sh no longer is downloaded from the internet has described at https://github.com/tinkerbell/tink/blob/master/docs/setup.md? |
The setup experience is being changed and the docs will follow shortly
afterwards.
On Tue, 16 Jun 2020 at 22:04, Rui Lopes ***@***.***> wrote:
Oh we now need to git clone the tink repo? The setup.sh no longer is
downloaded from the internet has described at
https://github.com/tinkerbell/tink/blob/master/docs/setup.md?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#172 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR3GYTTQYIGP2MY6YODIALRW7M5VANCNFSM4N76OCCQ>
.
--
Mark Coleman
+44(0)7367462394
|
Got it working at https://github.com/rgl/rpi-tinkerbell-vagrant/tree/wip-upgrade-tinkerbell. Some other day I will have to test whether the rpi provisioning still works. I have to say that the installation is now simpler to understand as the dependencies are explicit (curl, git, docker, docker-compose) and to start tinkerbell we can just use docker-compose up --detach. Nicely done! And hurrah to being able to directly use the docker logs command! I do not miss the heavyweight of ELK in the default setup. The only thing that was unexpected was the need to pre-create the directory at /etc/docker/certs.d/$provisioner_ip_address (see rgl/tinkerbell-vagrant@7b381fa#diff-f9e2dd117f9eb399ee41b4f867143dc2R23). |
I'm glad you find the new installation simpler to understand that was the idea. @grahamc May be able to address your certs concern. |
Why is git a pre-requirement in setup.sh?
The text was updated successfully, but these errors were encountered: