This repository was archived by the owner on Mar 11, 2025. It is now read-only.
Conversation
…-compose `--scale` argument.
Collaborator
|
Looks like good small change, thanks! |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
There is
--scaleparameter in docker-compose (docs) that allows to start several instances of certain container. It's not working in current implementation.Docker compose's
--scaleparameter is useful for running several container replicas in the same terminal window which is extremely handy for running on remote servers.Current behavior:
After running the following command:
I'm getting the following error:
Expected behavior
After running the following command:
no errors need to be thrown. Containers need to be scaled to 5 running instances in parallel.
Proposed solution
Now
scaleparameter does not respected by docker-compose because of strictly definedcontainer_nameandimageproperties inuashieldservice. Just removing them will resolve the problem and container names for replicas will not conflict with any other replicas.