docker-compose: fixes for local-dev mode #2010
Open
Conversation
This file contains hidden or 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
|
Can one of the admins verify this patch? |
On Docker Compose version 2.24.7 it fails with error: `"services.quay-notifier": container name "clair-notifier" is already in use by "services.notifier": invalid compose project` Signed-off-by: perat <[email protected]>
Workaround for issue quay#2009 suggested in docker/compose#1339 (comment) Signed-off-by: perat <[email protected]>
perat
force-pushed
the
release-4.7-docker-compose-fix
branch
from
28b25be to
d33f0f8
Compare
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.
Fixes:
"services.quay-notifier": container name "clair-notifier" is already in use by "services.notifier": invalid compose projectobserved on Docker Compose version 2.24.7open /tmp: operation not supported error