Closed ghost closed 4 years ago
This is the correct screenshot of the docker-compose up -d
command:
Hi @I-Lopez, I just ran the same setup on my local machine and it is working fine. There is no issue with boots. After looking at your logs I feel like there is a possibility that your boots image might not be the latest one. Could you please destroy the current vagrant setup completely and try that again and let us know if you face the same issue again?
Thanks,
This worked thank you!
I'm trying to run through the Vagrant guide, but Boots does not stand after running
docker-compose up -d
This screenshot shows the warnings once the above command is executed.
This one shows the results of
docker-compose ps
The results of the log command
docker-compose logs -f tink-server boots nginx
are below.Boots will try to deploy with the message
deploy_boots_1 exited with code 2
before trying again.Steps to Reproduce (for bugs)
Everything seems to work up until I run docker-compose commands.
Context
I'm trying to follow the Vagrant guides to mess around with Tinkerbell. I have tried using different network names in the envrc file to see if that has anything to do with it, but the results don't change from the ones shown above. Running the docker-compose commands as
sudo
make it so many of the envrc environment variables are blank strings.Your Environment
I'm running the latest version of MacOS Catalina. I'm following the Vagrant with Virtual Box guide. I'm not sure what other details can help, but I have Docker Desktop installed on my machine as well.
Thank you for the time.