5 ms·

rkt on the other hand is a dead project and completely useless to Red Hat. What support do you have for this statement? The github project is still pretty

by zaphar 9y ago

rkt on the other hand is a dead project and completely useless to Red Hat. What support do you have for this statement? The github project is still pretty active. The architecture appears to be far more sane. k8s supports it as well as docker for the runtime piece. And just anecdotally docker hasn't been the greatest experience for me running in production. So much so that I've considered exploring rkt as a replacement. I would not at all be surprised if RedHat was hedging their bets re: docker with this coreos acquisition.

zapita 9y ago
I'm sure rkt is well engineered (overall CoreOS has good open-source engineering). It just doesn't have much usage, and whatever advantages it has, evidently it wasn't enough to convince a meaningful number of Docker users to switch. I use Docker intensively and, like you, I've had my share of frustrating issues with it over the years. But at the end of the day, the bugs get fixed reasonably quickly, and Docker just gets the job done. Their code has so much mileage at this point, I just don't see the point in starting over with a competitor. Evidently I'm not the only one who feels that way.
- zaphar 9y ago
  I don't know. I wouldn't say my experience has been that the bugs get fixed reasonably quickly. It's more like they make several attempts to fix the bugs reasonably quickly and then eventually figure it out. I'm not sure their code has enough mileage to paper over their quality issues. At this point the only reason I'm not switching over is that I've written enough shims and code to paper over dockers problems that I have it somewhat stable and the switch cost is just barely high enough to make sticking with it the right choice for now. But it won't take too many more problems to make me reevaluate that decision.
  - zapita 9y ago
    It's surprising that our experiences were so different. Are you using CE or EE? And if it's CE, is it the upstream-supplied package or the distro-supplied one? In my experience those things can make a big difference.
    - zaphar 9y ago
      It's the distro supplied CE package.
jbronn 9y ago
I think it’s because RedHat has thrown its weight behind CRI-O instead of rkt: https://www.redhat.com/en/blog/introducing-cri-o-10 https://www.redhat.com/en/blog/introducing-cri-o-10

by zaphar 9y ago

zapita 9y ago

I'm sure rkt is well engineered (overall CoreOS has good open-source engineering). It just doesn't have much usage, and whatever advantages it has, evidently it wasn't enough to convince a meaningful number of Docker users to switch. I use Docker intensively and, like you, I've had my share of frustrating issues with it over the years. But at the end of the day, the bugs get fixed reasonably quickly, and Docker just gets the job done. Their code has so much mileage at this point, I just don't see the point in starting over with a competitor. Evidently I'm not the only one who feels that way.

zaphar 9y ago
I don't know. I wouldn't say my experience has been that the bugs get fixed reasonably quickly. It's more like they make several attempts to fix the bugs reasonably quickly and then eventually figure it out. I'm not sure their code has enough mileage to paper over their quality issues. At this point the only reason I'm not switching over is that I've written enough shims and code to paper over dockers problems that I have it somewhat stable and the switch cost is just barely high enough to make sticking with it the right choice for now. But it won't take too many more problems to make me reevaluate that decision.
- zapita 9y ago
  It's surprising that our experiences were so different. Are you using CE or EE? And if it's CE, is it the upstream-supplied package or the distro-supplied one? In my experience those things can make a big difference.
  - zaphar 9y ago
    It's the distro supplied CE package.

jbronn 9y ago

I think it’s because RedHat has thrown its weight behind CRI-O instead of rkt: https://www.redhat.com/en/blog/introducing-cri-o-10 https://www.redhat.com/en/blog/introducing-cri-o-10