-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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 setting a one-off container name #1930
Conversation
4c2bd00
to
95b6227
Compare
@@ -99,14 +99,12 @@ def test_get_volumes_from_service_no_container(self): | |||
|
|||
def test_split_domainname_none(self): | |||
service = Service('foo', image='foo', hostname='name', client=self.mock_client) | |||
self.mock_client.containers.return_value = [] |
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.
These mock return values haven't been necessary for a while, since we refactored _get_container_create_options()
to not make any api calls.
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.
Nice. Sorry to be picky, but would you mind doing this cleanup (and the __
-> _
changes) in a separate commit?
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.
Cool, I can do that
…ndard single underscore for unused variable Signed-off-by: Daniel Nephin <dnephin@gmail.com>
Signed-off-by: Daniel Nephin <dnephin@gmail.com>
95b6227
to
d2718be
Compare
Split into 2 commits, cleanup then actual feature |
LGTM |
Allow setting a one-off container name
In #1755 we removed the custom name from one-off containers, which left them with the default name.
This adds a
--name
param todocker-compose run
to name the container