djpbessems/Tinkerbell.Sandbox
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
one-touch-sandbox
Tinkerbell.Sandbox/README.md
Jacob Weinstock b3726acedf Move all glue scripts to bash: 
By using `/usr/bin/env sh` I needed to ignore some
shell checks. By moving to bash, those shell checks can
be re-enabled.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
2021-08-19 11:03:31 -06:00

1.8 KiB
Raw Permalink Blame History

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

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.

  1. Create Hardware Data
  2. Create a Template
  3. Create a Workflow

In the Sandbox

  1. Create your own templates

    docker exec -i compose_tink-cli_1 tink template create < ./custom-template.yaml

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

  3. 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"}')

  4. Restart the machine to provision (if using the vagrant sandbox test machine this is done by running vagrant destroy -f machine1 && vagrant up machine1)