Fix harvester container in the docker compose #59
+10
−3
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.
Make it so the harvester container is manually triggered instead of starting with
docker compose upIt is not a service, its a script that takes arguments, which are currently missing from the compose, so it will just fail with an error message asking to provide a repository URL to harvest
But that is for the people who can actually run it, because for now the metadata-crawler docker image is only built for amd64, there is no image available for arm64, so it fails to pull on macOS
I also added instruction to run the harvester container alongside the running stack in the readme
Right now many people need to comment out the harvester line in the compose file to be able to deploy the warehouse locally
@tobiasschweizer @Michal-Kolomanski