[xxxn]

goddamnit.

ive spent the last week learning about containers via rkt, having deliberately avoided the docker hype for the last few years.

ive mostly ported my setup to rkt, using acis because thats what all the rkt docs talk about. ive invested time into the 3rd party dgr build tool, which works really well and is based on acis, and cant be easily ported to oci. ive set up CI, deployment etc. now it turns out ive misunderstood the situation and im going to have to throw it all away at some point soon.

this is basically why i didnt bother picking up docker before. or is it moby now? yeah.

should have just stuck with openvz, vagrant and shell scripts, theyve worked fine for the best part of a decade.

[philips]

I am sorry if the docs were unclear. I filed an issue if you could comment on where you got off track building ACIs we will try to have someone in the community fix it up: https://github.com/rkt/rkt/issues/3745

[philips]

Just to clarify here: rkt has a roadmap to get full OCI support, and needs core developers (help wanted) to do the work. If anyone is interested please jump in on some of the issues: https://github.com/rkt/rkt/issues?q=is%3Aissue+is%3Aopen+oci...

[xxxn]

thanks. i made a comment.

i was worried i was going to go back and look at the docs and see numerous glaring advisories that I'd ignored, having opted instead to read blatantly out of date pages, but no, apart from a few vague parenthetical warnings the docs all talk about building and working with ACIs and the appc spec.

[coding123]

I wouldn't expect a different container tech to have the same bumps, but of course it's gonna have them too.