-
Notifications
You must be signed in to change notification settings - Fork 137
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 download link #519
Docker compose download link #519
Conversation
Signed-off-by: MaxPeal <[email protected]>
Signed-off-by: MaxPeal <[email protected]>
It looks like mergify is stuck on this validation phase. Is there any way to kick it? |
@displague - a force push should help. |
Also, I don't think this fixes #306 - which seemed to be around adding some kind of retry? Am I confused? |
@tstromberg Looks like this closes the issue described in #305 PR body, but not #306 which #305 was overextended to solve. |
Hey @displague, do you know where/when |
@jacobweinstock Good question. This PR was resurrected from another PR from a stale issue resurfaced through triage-party. It seems I may have applied a fix for a file we no longer use. It looks like setup.sh is no longer part of the directions (at least not in a GH search of this project). |
Description
Rebase of #305 (@MaxPeal) with reviewer requested changes applied.
notably, this variation on the original PR does not include
curl --progress
.Why is this needed
Fixes: #306
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: