4 ms·
It's unclear to me what this offers that runc or rkt do not offer. They say this : > railcar always runs an init process separately from the container process
by conradk 9y ago
It's unclear to me what this offers that runc or rkt do not offer. They say this :
> railcar always runs an init process separately from the container process
What does that mean in terms of day to day operations/debugging ? What are the benefits ?
- rndmio 9y agoOne thing it means is no zombies in the process table. When you're running something like squid in a container and you HUP it to reload the config (volume mounted) without something to reap the old process you're going to have zombies.
- vishvananda 9y agoAuthor here. For more discussion on init handling you may find my article on pid namespaces[1] enlightening. In terms of differences from runc, there aren't many. The goals for railcar are threefold: 1: provide an alternative implementation of the oci-runtime so that the spec doesn't become too locked to a single implementation. 2: provide an implementation in a single language without some of the "baggage" of the existing implentations so that it is easy and fun to hack on. 3: experiment with new ideas to inform the future of the oci-runtime spec. [1] https://hackernoon.com/the-curious-case-of-pid-namespaces-1ce86b6bc900 https://hackernoon.com/the-curious-case-of-pid-namespaces-1c...