-
Notifications
You must be signed in to change notification settings - Fork 273
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
0.13: [Bug]: quickstart-example
, when run on k3s, fails on first deploy only
#4460
Comments
@Orzelius, this problem is also present on Killercoda example; I'm using Ubuntu 18.04 with a k3s cluster; First deploy will fail and then the second deployment succeeds, To reproduce this, just access the Killercoda environment and follow the steps until the https://killercoda.com/shankyjs/course/scenarios/getting-started I couldn't reproduce this locally |
@worldofgeese I can't reproduce this, because Cloud Shell init fails when it tries to clone the remote repo (I tried 3 times): This this a know issue? |
The link was fixed "in prod" (on our docs site). I've now fixed it for the Cloud Shell button in this issue. Can you try again? |
@worldofgeese thanks! Now I can open the project in the Cloud Shell. By the way, |
@vvagaytsev did you follow along with the tutorial on the right sidepane? I just tried and it works. The tutorial must be followed in order. |
@worldofgeese sorry, I might have missed some details from the tutorial :) I'll try it later. Anyway, the problem with repo cloning has gone. The fix from #4657 should fix this. |
The fix will be released today in Garden |
@vvagaytsev thank you so much for this fix! 💚 |
@vvagaytsev I have reproducible examples and guides for setting up test environments for k3s, k3d, and Rancher Desktop together with error messages for each at #4528. if you use Multipass on macOS, you can spin up an Ubuntu VM very easily with this tutorial to test k3s and k3d. Rancher Desktop is macOS compatible OOTB. |
Garden Bonsai (0.13) Bug
Current Behavior
One issue I encountered was the postgres deploy failing and not re-trying (this happened again on a brand new Cloud Shell and I don't know why):
I just ran
deploy
again, which successfully deployed all services the second time:Originally posted by @worldofgeese in garden-io/quickstart-example#6 (comment)
Reproducible example
Workaround
Run
deploy
a second time.The text was updated successfully, but these errors were encountered: