-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Integration Testing] PEcAn Docker Stack Run : Single Site, Single Model #3345
base: develop
Are you sure you want to change the base?
[Integration Testing] PEcAn Docker Stack Run : Single Site, Single Model #3345
Conversation
Co-authored-by: Chris Black <[email protected]>
Co-authored-by: Rob Kooper <[email protected]>
611ddbb
to
eb896d1
Compare
Co-authored-by: Chris Black <[email protected]>
@@ -62,6 +62,10 @@ jobs: | |||
sleep 50 | |||
docker ps | |||
|
|||
- name: Add models | |||
run: | | |||
docker compose exec --workdir /pecan/scripts executor sh add.models.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Latest logs are showing that the executor image doesn't have psql installed.
There are probably better ways, but I think this should work:
docker compose cp scripts/add.util.sh postgres:/tmp/add.util.sh
docker compose cp scripts/add.models.sh postgres:/tmp/add.models.sh
docker compose exec postgres /tmp/add.models.sh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting to suspect I'm sending you on a goose chase here. Hey @robkooper is this the right approach or should we instead be, like, starting the monitor service and waiting for it to register sipnet for us? If so what would that look like here?
Description
PR aims at adding a workflow for running a complete PEcAn workflow using PEcAn's docker stack.
Review Time Estimate
Types of changes
Checklist: