You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since kaws is tied to CoreOS and it's safe to say CoreOS will have the best possible support for rkt, we should use rkt as k8s's container runtime instead of Docker, as soon as rkt is 1.0. rkt has much saner tooling (acbuild is significantly better than Dockerfiles) and a better security story (doesn't run as a daemon, signed images, doesn't require a registry, etc.) rkt can run Docker images as well so this change will not preclude the use of Docker images.
The text was updated successfully, but these errors were encountered:
Since kaws is tied to CoreOS and it's safe to say CoreOS will have the best possible support for rkt, we should use rkt as k8s's container runtime instead of Docker, as soon as rkt is 1.0. rkt has much saner tooling (acbuild is significantly better than Dockerfiles) and a better security story (doesn't run as a daemon, signed images, doesn't require a registry, etc.) rkt can run Docker images as well so this change will not preclude the use of Docker images.
The text was updated successfully, but these errors were encountered: