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

Why is git a pre-requirement in setup.sh? #172

Closed
rgl opened this issue Jun 16, 2020 · 5 comments
Closed

Why is git a pre-requirement in setup.sh? #172

rgl opened this issue Jun 16, 2020 · 5 comments

Comments

@rgl
Copy link
Contributor

rgl commented Jun 16, 2020

Why is git a pre-requirement in setup.sh?

@rgl
Copy link
Contributor Author

rgl commented Jun 16, 2020

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?

@mrmrcoleman
Copy link
Contributor

mrmrcoleman commented Jun 16, 2020 via email

@rgl
Copy link
Contributor Author

rgl commented Jun 16, 2020

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).

@mrmrcoleman
Copy link
Contributor

I'm glad you find the new installation simpler to understand that was the idea.

@grahamc May be able to address your certs concern.

@grahamc
Copy link
Contributor

grahamc commented Jun 17, 2020

Git as a requirement: good catch. It isn't needed anymore. I dropped it in #173

Certs directory: I hit this yesterday and forgot to open a PR. I fix it in #174

I'm glad the docker logs option is good for you! Hopefully it saves a lot of time for everybody. Also, the updated docs are indeed coming.

@grahamc grahamc closed this as completed Jun 17, 2020
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

3 participants