|
|
|
|
|
by OJFord
2084 days ago
|
|
So this is also an issue (by which I mean something to be aware of, that I think most aren't) with Linux docker containers on Windows/macOS? It makes perfect sense now you say it - I knew hyper-v was a hypervisor, I knew in basic broad strokes what a hypervisor is and where it sits, but for some reason this didn't occur to me. It could be very alarming to people running containers 'on a Windows' server, but then such people are probably more familiar with hypervisors anyway. Is hyper-v networking still somehow configurable from the 'host', or is it undesirable for containers unless you don't want to do anything to the network (in software on that machine)? |
|