-
Notifications
You must be signed in to change notification settings - Fork 85
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
"docker-compose up -d" step failing with error "sync-images-to-local-registry container "0d851d894440" is unhealthy" #148
Comments
I resolved that on sandbox\deploy\compose\sync-images-to-local-registry\upload.sh, adding |
@gabrielbarata , Thanks a lot for the response. Copy/pasting the snippet from upload.sh below:
( I am seeing same error in Ubuntu also. Code snippet given above is from Ubuntu ) |
Can you run |
@gabrielbarata , I ran the command you gave but I am not seeing any logs getting displayed. Please find the console ouput.
|
## Description This PR brings up the sandbox via Docker compose using the Kubernetes backend for all service. This does not completely remove the postgres backend setup but moves all the compose with postgres into an isolated directory (deploy/compose/postgres) that can be removed when we're ready. > I did not touch the terraform setup. I need some help validating that one. please and thank you. CC @mmlb @displague ## Why is this needed Fixes: #142 #45 #118 #131 #133 #145 #148 - This "fixes" a quite a few issues related to TLS cert generation. This is the case because we are not using TLS in this deployment. Also see, tinkerbell/tink#555. - This also "fixes" any issues related to the internal registry as that is removed as the default. ## How Has This Been Tested? Manually tested vagrant with virtualbox (on a Mac), vagrant with libvirt (on Ubuntu 22.04), and docker-compose (on on Ubuntu 22.04). ## How are existing users impacted? What migration steps/scripts do we need? There is no migration support. Users will need to follow a quick start guide to get started. ## Checklist: I have: - [x] updated the documentation and/or roadmap (if required) - [ ] added unit or e2e tests - [ ] provided instructions on how to upgrade
I am trying out steps to bring-up Tinkerbell on baremetal server with Windows 2019 installed. I am following steps mentioned in location "https://github.com/tinkerbell/sandbox/blob/main/docs/quickstarts/COMPOSE.md".
In the above location at Step-4, after executing "docker-compose up -d" command, getting following error and not able to proceed.
ERROR : for sync-images-to-local-registry container "0d851d894440" is unhealthy.
ERROR: Encountered errors while bringing up the project.
Expected Behaviour
Step-4 should complete with out errors and should be able to start the provisioner successfully and proceed further bring up of new machine.
Current Behaviour
Getting error in step-4 as explained above.
Possible Solution
Steps to Reproduce (for bugs)
Refer : https://github.com/tinkerbell/sandbox/blob/main/docs/quickstarts/COMPOSE.md
Context
I am trying to bring-up test machine.
Your Environment
Trying to setup provisioner on Windows 2019 DC.
Running Tinkerbell on baremetal
The text was updated successfully, but these errors were encountered: