increase configbaker timeout #9886
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
poikilotherm
added
the
Component: Containers
poikilotherm
approved these changes
Sep 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
@nightowlaz was brave enough to try
docker compose -f docker-compose-dev.yml upfrom https://guides.dataverse.org/en/5.14/container/dev-usage.html#running BUT it didn't work! :homer-doh:In this thread we figured out the a 3 minute time out is better than 2 (so I'm bumping it):
https://dataverse.zulipchat.com/#narrow/stream/375812-containers/topic/running.20using.20compose
Which issue(s) this PR closes:
None
Special notes for your reviewer:
This issue is related:
Suggestions on how to test this:
Try the docker compose command above. Does it work? In the before/failure case you might see this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No
Is there a release notes update needed for this change?:
No
Additional documentation:
No