News for hackers. Stuff that matters.
Re:Unikernels are unfit for production by misterbisson on Friday January 22, 2016 @12:22PM (#10954090)
What if you could have isolation that's as good as or better than a VM in a container?
Re:Unikernels are unfit for production by lmm on Friday January 22, 2016 @02:02PM (#10954814)
Then I'd be interested. But Solaris is x million lines of C code and the system call attack surface is huge, so I really don't think Joyent can offer that. Fundamentally if the author believes that you need a full traditional unix userland inside the container for debugging then they're never going to be able to offer that level of isolation.
Re:Unikernels are unfit for production by cyphar on Saturday January 23, 2016 @08:01AM (#10958249)
Not inside the container. Containers are transparent to the host (Zones especially). You have tooling in the kernel, and you take coredumps when a container process dies.
Re:Unikernels are unfit for production by lmm on Sunday January 24, 2016 @01:02PM (#10963278)
See that's the model I'd expect to take - but that model makes perfect sense in the unikernel world too. So the author must be claiming that you need the debugging tools inside the container, otherwise the point about not having tcpdump etc. available makes no sense.
Re:Unikernels are unfit for production by cyphar on Wednesday January 27, 2016 @08:22PM (#10985284)
The problem with applying the same logic to hypervisor'd unikernels is that hypervisors make the guest system opaque. So how could you meaningfully run DTrace on that system?
Re:Unikernels are unfit for production by marssaxman on Saturday January 23, 2016 @02:44PM (#10959732)
How would that be possible? If you have a container with an attack surface as small as a VM, haven't you basically just created a VM by another name?