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.

Sign up for GitHub

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

Jump to bottom

Don't stop an existing container automatically #4

Open
kparkov opened this issue Nov 1, 2019 · 0 comments
Open

Don't stop an existing container automatically #4

kparkov opened this issue Nov 1, 2019 · 0 comments
Labels
bug Something isn't working
Milestone
Stable release

Comments

@kparkov
Copy link
Member

kparkov commented Nov 1, 2019

Right now, calling New-SqlDockerContainer will remove any existing container using the mssql name.

The expected behaviour is to not stop any existing container, but instead raise an error if there is a container name or port collision.
@kparkov kparkov added this to the Stable release milestone Nov 1, 2019
@kparkov kparkov added the bug Something isn't working label Nov 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Stable release
Development

No branches or pull requests
1 participant
@kparkov