djpbessems/Tinkerbell.Sandbox
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
6b841fee7c
Tinkerbell.Sandbox/deploy/compose/registry/registry_images.txt

4 lines
166 B
Plaintext
Raw Normal View History

This simplifies the stand-up of a sandbox: Only 2 main Vagrant calls are now needed (`vagrant up` and `vagrant up machine1`). This PR only updates the Vagrant Virtualbox setup. The Vagrant Libvirt and Terraform still need to be updated. This uses docker-compose as the entry point for standing up the stack and makes the stand-up of the sandbox more portal. Vagrant and Terraform are only responsible for standing up infrastructure and then running docker-compose, not for running any glue scripts. The docker-compose calls out to single-shot services to do all the glue required to get the fully functional Tinkerbell stack up and running. All the single-shot services are idempotent. This increases portability and the development iteration loop. This also simplifies the required steps needed to get a fully functioning sandbox up and running. This is intended to help people looking to get started by getting them to a provisioned machine quicker and more easily. Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>
2021-08-09 14:04:06 +00:00
quay.io/tinkerbell/tink-worker:latest
quay.io/tinkerbell-actions/image2disk:v1.0.0
quay.io/tinkerbell-actions/cexec:v1.0.0
quay.io/tinkerbell-actions/writefile:v1.0.0
Reference in New Issue Copy Permalink