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 containers to be named using its 'alias' #115

Merged
merged 1 commit into from
Mar 20, 2015

Conversation

jgangemi
Copy link
Collaborator

@jgangemi jgangemi commented Mar 1, 2015

  • allow container to be named using alias when created/started

Signed-off-by: Jae Gangemi [email protected]

- allow container to be named using `alias` when created/started

Signed-off-by: Jae Gangemi <[email protected]>
@rhuss
Copy link
Collaborator

rhuss commented Mar 19, 2015

Do you intend to implement the other namingSchemes, too ? If not I'll try to work on them (or at least open an issue so they are not forgotten ;-) Currenlty, an error occurs if docker:start is called twice (which is probably expected).

@jgangemi
Copy link
Collaborator Author

for now i think we should just file a separate issue for the other schemes. no one else seems to be clamoring for this and what's been implemented meets my needs.

an error is expected if docker:start is called twice. this is inline w/ how the docker binary works.

rhuss added a commit that referenced this pull request Mar 20, 2015
I.e. that an error is thrown if a container already exists with this name. #48 #115
@rhuss rhuss merged commit 7ce4fd5 into fabric8io:integration Mar 20, 2015
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