Fix docker compose file #267
Closed
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
|
As discussed, the issue in this case is the volumes aren't cleared on each run, so the NEAR CLI data already exists even though the localnet is reset. Closing this for now and I should open a new PR soon. |
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.
Current Behavior
The
docker compose upcommand currently fails during the startup of theindexer-setupcontainer. As a result, therelayercontainer do not run, leading to incorrect system operation. This failure occurs because theindexer-setupcontainer attempts to deploy contracts that already exist in initial state.New Behavior
Remove the
indexer-setupcontainer entirely from the system.Breaking Changes
No breaking changes are expected.