-
Notifications
You must be signed in to change notification settings - Fork 87
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 quickstart breaks with ERROR: Invalid interpolation format for "tls-gen" option in service "services": "${FACILITY:-onprem}" #118
Comments
Hey @dch, thanks for reporting this. Were you following this guide by chance? https://github.com/tinkerbell/sandbox/blob/main/docs/quickstarts/COMPOSE.md |
Yea a bit of this and perusing the vagrantfile from libvirt approach
…On Thu, 2 Dec 2021, at 17:49, Jacob Weinstock wrote:
Hey @dch <https://github.com/dch>, thanks for reporting this. Were you
following this guide by chance?
https://github.com/tinkerbell/sandbox/blob/main/docs/quickstarts/COMPOSE.md
It does mention a docker-compose version requirement, but maybe we need
to present that in a different way.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACFNUBEZKTRVA7QACQDNKDUO6PSBANCNFSM5I5LHOFA>.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hey @dch. Based on your experience here, would you be willing to provide any feedback on what we could do to make the docker-compose version requirement more apparent? |
I had similar error prompt while running: docker-compose ps Later, realized that I did not run: cd /vagrant/compose first. /vagrant is Synced Folder defined in Vagrant file: provisioner.vm.synced_folder '../', '/vagrant' |
## 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
## 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: tinkerbell#142 tinkerbell#45 tinkerbell#118 tinkerbell#131 tinkerbell#133 tinkerbell#145 tinkerbell#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
Expected Behaviour
Current Behaviour
Possible Solution
I think the precise version docker-compose needs to be specified. 2.x is already public, 1.26 is too old, and 1.29.2 works for me.
Steps to Reproduce (for bugs)
Context
I was trying the simplest way to get to a running tinkerbell setup, assuming that docker-compose might be a good starting point.
Your Environment
using an ubuntu 20.04.3 LTS VM.
ubuntu vm
n/a
The text was updated successfully, but these errors were encountered: