Repository navigation
Installer: time limit on docker compose up (#376) - #378
Merged
Merged
Conversation
This file contains hidden or 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
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.
Closes #376.
What
docker compose up -d --buildfor the Endpoint and for the bundled CKAN now runs undertimeout. The limit is set with--compose-timeout <n>(minutes, or seconds with anssuffix); the default is 30 minutes and0means no limit.docker pull, check the Docker Hub rate limit and any proxy, then re-run. The message also mentions--compose-timeout.timeout(coreutils) there is no limit, and the installer warns about it.Tests
install/tests/test_compose_timeout.py: 10 tests, 6 of which fail onmain.--compose-timeout 2sthe real image build was stopped after 3s with the message;Release 0.34.60.