Skip to content
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

Allow docker-compose down to "fail" as the services might have significantly changes #277

Merged
merged 1 commit into from
Oct 18, 2022

Conversation

aforward
Copy link
Contributor

When testing against branch 294-load-data-after-up

If you run

docker-compose -f eclipse-pass.base.yml -f eclipse-pass.demo.yml down

If will fail because the compose changed soooo much.

ERROR: The Compose file is invalid because:
Service ember has neither an image nor a build context specified. At least one must be provided.

So it should be OK for the "down" to fail and not fail the deploy.

…icantly changes

When testing against branch `294-load-data-after-up`

If you run

```
docker-compose -f eclipse-pass.base.yml -f eclipse-pass.demo.yml down
```

If will fail because the compose changed _soooo much_.

```
ERROR: The Compose file is invalid because:
Service ember has neither an image nor a build context specified. At least one must be provided.
```

So it should be OK for the "down" to fail and not fail the deploy.
Copy link
Contributor

@jabrah jabrah left a comment

Choose a reason for hiding this comment

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

Shouldn't happen, but for the best to guard against

@aforward aforward merged commit 495c580 into main Oct 18, 2022
@aforward aforward deleted the 294-allow-errors-when-stopping-current-system branch October 18, 2022 23:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants