2 ms·
Rkt took deliberate aim at the problem of reliably running docker containers as systemd services, and as one of the early rkt developers I can honestly say I di
by pengaru 5y ago
Rkt took deliberate aim at the problem of reliably running docker containers as systemd services, and as one of the early rkt developers I can honestly say I did so grudgingly after various meetings convincing me we had no choice.
If the Docker folks hadn't deliberately obstructed our ability to reliably run Docker containers as systemd services, none of this would have been necessary. We certainly had better things to spend our time on.
- mixmastamyk 5y agoI never understood why Rocket was killed, when it seemed to be a better design. Was it because Red Hat was already pushing podman and didn't need two tools doing similar things?
- dralley 5y agoI'm not the person you asked, but another rkt dev answered a similar question last year https://news.ycombinator.com/item?id=22250270 https://news.ycombinator.com/item?id=22250270
- deleted 5y ago[deleted]
- pengaru 5y agoNot sure, I was no longer involved when those changes were happening. What I can say is there was a lot of change in the container landscape at the time. Kubernetes flipped the script, Fleet from CoreOS was deprecated, and my guess is amidst the consolidation happening around Kubernetes and the CNCF, rkt became less relevant and just didn't find a permanent home. Flannel, Fleet, Rocket... does anyone use any of this stuff still? "Move fast and break things" tends to leave a trail of waste in its wake.