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

Don't use custom name for one-off containers #1755

Merged
merged 1 commit into from
Jul 22, 2015

Conversation

aanand
Copy link

@aanand aanand commented Jul 22, 2015

Closes #1753.

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
@dnephin
Copy link

dnephin commented Jul 22, 2015

While this fixes the immediate problem. I know there are cases where I'd actually want this custom name for the one off. Maybe we could add --name to docker-compose run allowing naming of one-off containers? I guess it doesn't need to happen right now.

@dnephin
Copy link

dnephin commented Jul 22, 2015

LGTM

aanand added a commit that referenced this pull request Jul 22, 2015
Don't use custom name for one-off containers
@aanand aanand merged commit fc32cce into docker:master Jul 22, 2015
aanand added a commit to aanand/fig that referenced this pull request Jul 22, 2015
Don't use custom name for one-off containers
(cherry picked from commit fc32cce)

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
aanand added a commit to aanand/fig that referenced this pull request Jul 23, 2015
Don't use custom name for one-off containers
(cherry picked from commit fc32cce)

Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants