3 ms·

Does anyone use rkt?

philips 10y ago
A few data points: - Laptop Kubernetes, minikube, can use rkt with a single flag https://github.com/kubernetes/minikube#using-rkt-container-engine https://github.com/kubernetes/minikube#using-rkt-container-e... - BlaBlaCar rkt in prod and moving to Kubernetes - Container Linux by CoreOS services like kubelet and etcd now run using rkt and download docker images from quay.io - GKE ContainerVM is looking to use rkt for Kubelet mount management
jat850 10y ago
Using rkt with kubernetes, yes. This article gives some meaningful insight. There's been a lot of hoop jumping, but rkt has several critical features that make it the right fit for us.
- monatron 10y ago
  If possible, can you elaborate on those critical features?
  - jat850 10y ago
    Sorry, didn't notice your response. Email's in profile if you want to hear some of our use cases!
    - zwischenzug 10y ago
      I'd like to hear too, and prob others.
meddlepal 10y ago
Rkt really is missing good on-boarding / Getting Started instructions. I don't have time to figure out all the details and I really want to know how to do the following things: 1. Create Dockerfile like equivalents for Rkt images 2. Share and publish Rkt images. 3. Consume Rkt images in a Kube cluster that already supports Docker on AWS.
- philips 10y ago
  rkt executes docker images and OCI images: https://coreos.com/rkt/docs/latest/running-docker-images.html https://coreos.com/rkt/docs/latest/running-docker-images.htm...
- wyldfire 10y ago
  I gave it a try. The docs are good, but they could definitely be better [1]. I found a couple doc errors and got PRs merged quickly. [1] https://github.com/coreos/rkt/blob/master/Documentation/trying-out-rkt.md#building-an-app-container-image https://github.com/coreos/rkt/blob/master/Documentation/tryi...
  - meddlepal 10y ago
    Thanks!
- nikolay 10y ago
  The Dockerfile is my biggest issue with Docker. I really don't like to write shell scripts in there, but there are caching benefits (thanks to the limitations of Docker) to inline everything in there. Although the idea is to have an endless chain of dependent images with small Dockerfiles on each step, the reality is different. I recently needed a monolithic image of having Nginx, Node.js, and Phusion Passenger, just merging the Dockerfiles doesn't work as each has a cleanup step that ruins things for the next one. I know it's great to have everything self-contained (pun intended) in a single Dockerfile - it's much easier to diff and display on Docker Hub, but this promotes bad practices without a doubt!
mtanski 10y ago
Yeah, we're in the process of moving some of our services from docker to rkt. We're about 1/2 way done and all new ones are being deployed on rkt. We've been hit by to many regressions docker versions and issues with docker daemon that required us to restart docker and all the containers on a host. One systemd unit -> rkt container -> our service is just such a better failure domain. We're currently running containers outside of explicit container orchestration like k8 or docker compose. But in the future we'll be moving some of our elastic workloads to k8 and in the long term almost everything but services that rely on persistent data on lock disk (where network block device doesn't cut it).

A few data points: - Laptop Kubernetes, minikube, can use rkt with a single flag https://github.com/kubernetes/minikube#using-rkt-container-engine https://github.com/kubernetes/minikube#using-rkt-container-e... - BlaBlaCar rkt in prod and moving to Kubernetes - Container Linux by CoreOS services like kubelet and etcd now run using rkt and download docker images from quay.io - GKE ContainerVM is looking to use rkt for Kubelet mount management

jat850 10y ago

Using rkt with kubernetes, yes. This article gives some meaningful insight. There's been a lot of hoop jumping, but rkt has several critical features that make it the right fit for us.

monatron 10y ago
If possible, can you elaborate on those critical features?
- jat850 10y ago
  Sorry, didn't notice your response. Email's in profile if you want to hear some of our use cases!
  - zwischenzug 10y ago
    I'd like to hear too, and prob others.

meddlepal 10y ago

Rkt really is missing good on-boarding / Getting Started instructions. I don't have time to figure out all the details and I really want to know how to do the following things: 1. Create Dockerfile like equivalents for Rkt images 2. Share and publish Rkt images. 3. Consume Rkt images in a Kube cluster that already supports Docker on AWS.

philips 10y ago
rkt executes docker images and OCI images: https://coreos.com/rkt/docs/latest/running-docker-images.html https://coreos.com/rkt/docs/latest/running-docker-images.htm...
wyldfire 10y ago
I gave it a try. The docs are good, but they could definitely be better [1]. I found a couple doc errors and got PRs merged quickly. [1] https://github.com/coreos/rkt/blob/master/Documentation/trying-out-rkt.md#building-an-app-container-image https://github.com/coreos/rkt/blob/master/Documentation/tryi...
- meddlepal 10y ago
  Thanks!
nikolay 10y ago
The Dockerfile is my biggest issue with Docker. I really don't like to write shell scripts in there, but there are caching benefits (thanks to the limitations of Docker) to inline everything in there. Although the idea is to have an endless chain of dependent images with small Dockerfiles on each step, the reality is different. I recently needed a monolithic image of having Nginx, Node.js, and Phusion Passenger, just merging the Dockerfiles doesn't work as each has a cleanup step that ruins things for the next one. I know it's great to have everything self-contained (pun intended) in a single Dockerfile - it's much easier to diff and display on Docker Hub, but this promotes bad practices without a doubt!

mtanski 10y ago

Yeah, we're in the process of moving some of our services from docker to rkt. We're about 1/2 way done and all new ones are being deployed on rkt. We've been hit by to many regressions docker versions and issues with docker daemon that required us to restart docker and all the containers on a host. One systemd unit -> rkt container -> our service is just such a better failure domain. We're currently running containers outside of explicit container orchestration like k8 or docker compose. But in the future we'll be moving some of our elastic workloads to k8 and in the long term almost everything but services that rely on persistent data on lock disk (where network block device doesn't cut it).