5 ms·
The plan for containers on Solaris, after rejecting injecting libc from the host, was to have users rebuild all containers after OS upgrade. Windows has to virt
by justincormack 7y ago
The plan for containers on Solaris, after rejecting injecting libc from the host, was to have users rebuild all containers after OS upgrade. Windows has to virtualise containers with an incompatible OS version. It is definitely less convenient than Linux.
OpenBSD does have somewhat different constraints and they seem to think this will work for them.
- xenadu02 7y agoThe iOS Simulator does something along these lines for macOS. When macOS is updated CoreSimulator rebuilds the dyld_sim shared caches because simulator runtimes pull in libsystem_kernel, libsystem_pthread, and libsystem_platform (which cover the core of the kernel’s ABI).
- binarycrusader 7y agoThe plan for containers on Solaris, after rejecting injecting libc from the host, was to have users rebuild all containers after OS upgrade. What containers are you referring to? Because this is definitely not how Zones work on Solaris. There are two types of Zones in Solaris 11; "Kernel Zones" which run their own independent version of Solaris and "non-global Zones" which are automatically kept at the same version as the host. Windows has to virtualise containers with an incompatible OS version. Not as far as I'm aware. Windows Sandboxes don't work that way nor do other technologies I'm aware of. What are you referring to?
- justincormack 7y agoThis was Docker containers, which were under development, and I think one version shipped. Windows containers have to run under hyper-v for incompatible kernel versions.