0ff1d633cd
With the recent update in Hook to publish the kernel and initrd we can make make hook the default in the sandbox. Original OSIE can still be used by updating deploy/compose/.env and setting OSIE_DOWNLOAD_URL to an OSIE URL and TINKERBELL_USE_HOOK to false. Currently only an x86_64 Hook is published so only x86_64 machines can be provisioned with the sandbox using Hook. Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
Quick-Starts
The following quick-start guides will walk you through standing up the Tinkerbell stack. There are a few options for this. Pick the one that works best for you.
Options
- Vagrant and VirtualBox
- Vagrant and Libvirt
- Docker Compose
- Terraform and Equinix Metal
- Kubernetes
- Multipass
Next Steps
Now that you have a Tinkerbell stack up and running, you can start provisioning machines. Tinkerbell.org has a list of guides for provisioning machines. You can also create your own. The following docs will help you get started.
In the Sandbox
-
Create your own templates
docker exec -i compose_tink-cli_1 tink template create < ./custom-template.yaml -
Upload any container images you want to use in the templates to the internal registry
docker run -it --rm quay.io/containers/skopeo copy --all --dest-tls-verify=false --dest-creds="admin":"Admin1234" docker://hello-world docker://192.168.50.4/hello-world -
Create a workflow
docker exec -i compose_tink-cli_1 tink workflow create -t <TEMPLATE ID> -r '{"device_1":"08:00:27:00:00:01"}') -
Restart the machine to provision (if using the vagrant sandbox test machine this is done by running vagrant destroy -f machine1 && vagrant up machine1