Skip to content

Conversation

@vemonet
Copy link
Collaborator

@vemonet vemonet commented Feb 11, 2026

Make it so the harvester container is manually triggered instead of starting with docker compose up

It 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

… of starting with `docker compose up`. It is not a service, its a script that takes arguments (which are currently missing from the compose). Added instruction to run the harvester container in the readme
@vemonet vemonet added the bug Something isn't working label Feb 11, 2026
@vemonet vemonet requested a review from jos-no February 11, 2026 15:21
@tobiasschweizer
Copy link
Collaborator

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

Could we add a multi-platform image build so it works cross-platform? I guess that would need to happen here: https://github.com/EOSC-Data-Commons/metadata-crawlers/blob/master/.github/workflows/docker-publish.yml

Copy link
Collaborator

@Michal-Kolomanski Michal-Kolomanski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏

After starting the stack with `docker compose up`, you can run the harvester for a given repository URL, e.g.:

```sh
docker compose run harvester https://lifesciences.datastations.nl/oai
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is run by crontab, this might require an absolute path to the docker compose file: docker compose --project-directory /abs/path/to/dir run harvester https://lifesciences.datastations.nl/oai

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants