Repository navigation
docker run --isolation parameter not available #3906
Description
docker run has a parameter --isolation that can be used to set additional isolation modes when running Docker containers. For example, docker run --isolation=hyperv is commonly used on Windows with Hyper-V. Given that most of the other run options are already supported such as security_opt and privileged, I think it makes sense that isolation should be there too.
Here's an example of how I would like to use it in docker-compose.yml:
version: '2'
services:
sql:
image: windowsservercore
tty: true
stdin_open: true
# isolation: 'hyperv'
web:
image: windowsservercore
tty: true
stdin_open: true
# isolation: 'hyperv'
networks:
default:
external:
name: nat
Activity
PatrickLang commentedon Sep 2, 2016
ping @friism - can you tag this for Windows?
friism commentedon Sep 3, 2016
@PatrickLang what's the behavior when
hypervis not available? It would be sad if adding this option caused some docker-compose.yml files to only work on some systems.friism commentedon Sep 3, 2016
@PatrickLang (I'm not an admin here, so can't label)
PatrickLang commentedon Sep 3, 2016
re:
hypervnot available - I think that's ok. I view Dockerfiles as code that should have no dependency on environment. I expect to customize docker-compose files for my environment. For example,ipam,volume_driver,ipv4_address,loggingcan all contain data that will only work right in a specific deploymentuday31in commentedon Sep 13, 2016
What is the correct way to specify isolation setting with compose? I have a Front end that can use process isolation however back end service needs to on server core due to .Net 3.5 dependency and hosts are Nano.
friism commentedon Sep 22, 2016
@PatrickLang
Agree, it makes sense to include