3 ms·

Would this be a viable alternative to containers?

• the8472 9y ago
  from the documentation it sounds like it uses namespaces where available, just like containers. chroot otherwise.
  • nerdponx 9y ago
    I was actually wondering what advantage this has over a container or chroot. The answer is that it actually is one of those under the hood?
    • lima 9y ago
      Yes, it is. Either a magic user-space chroot, a normal chroot or user namespaces.
    • d-- 9y ago
      I've tested JuNest extensively (with the idea of getting new gcc compiler features on a cluster running an old red hat version). Unfortunately, JuNest adds a lot more overhead than containers. Specifically, when it comes to high-throughput network applications. At 10GBit an application running on JuNest used several cores at 100%, while without JuNest (underlying red hat) the app was at 10% cpu load (network i/o bound). All that load was due to PRoot.
      • da02 9y ago
        Have you tried with Linux namespaces instead of PRoot? https://github.com/fsquillace/junest#linux-namespaces-based https://github.com/fsquillace/junest#linux-namespaces-based