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

Support for: isolation #438

Closed
cdrage opened this issue Feb 22, 2017 · 6 comments
Closed

Support for: isolation #438

cdrage opened this issue Feb 22, 2017 · 6 comments
Labels
compose v2.1 libcompose

Comments

@cdrage
Copy link
Member

cdrage commented Feb 22, 2017 •
edited
Loading

No error / warning when using this key.
@procrypt
Copy link

procrypt commented Mar 1, 2017

@cdrage isolation has only one value for Linux which is default and for windows it has a some value to pick from like process, hyperv and default. The doc says this option is useful in situations where you are running Docker containers on Windows.
Do we need to add support for this? Reference

@kadel
Copy link
Member

kadel commented Mar 1, 2017

It doesn't make sense to map this to Kubernetes. We can display warning if it is set to something else than default.
But I wouldn't worry about that for now. I don't think that this is used.

@procrypt
Copy link

procrypt commented Mar 2, 2017

Can we close this issue?

@kadel
Copy link
Member

kadel commented Mar 2, 2017 •
edited
Loading

one note here. isolation is in compose version 2.1 and up.
2.1 is not yet supported by libcompose.

@surajnarwade
Copy link
Contributor

surajnarwade commented May 9, 2017 •
edited
Loading

@kadel , @cdrage label, compose v2.1 and libcompose needed

@cdrage
Copy link
Member Author

cdrage commented Aug 18, 2017

Closing this as we are not supporting it 👍

@cdrage cdrage closed this as completed Aug 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compose v2.1 libcompose
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kadel @surajssd @cdrage @procrypt @surajnarwade