3 ms·
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 f
by 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 agorkt 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 agoI 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 agoThanks!
- nikolay 10y agoThe 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!