rpm-ostree-toolbox shouldn't require certain packages to be present

[chrisruffalo]

So, maybe I'm crazy (or I'm looking at things the wrong way) but I was experimenting with using rpm-ostree to build a minimal Docker image. I feel like, when using a Dockerfile, it's a bit of a hack to use yum to download and install RPMs on the fly.

While trying to use rpm-ostree-toolbox to compose a tree I first had issues with the kernel (without the kernel package there's no /boot) and then later with the missing isci package (which I fixed by removing those flags for initd).

I eventually was successful but I just manually deleted a bunch of stuff and then recommitted those changes. I was able to import that same base commit (using ostree checkout) into Docker. (I had earlier tried removing those packages in the post-compose script but I got a strange error that I'm willing to look into later and I don't wan't to confuse this issue with.)

What I'm saying is that I'd like rpm-ostree-toolbox to be able to compose a tree without requiring these other packages. I'm not sure how that would be configured. (In the ini?)

(Or I'd like someone to tell me I'm crazy.)

[cgwalters]

To make an ostree commit, you just need rpm-ostree, not rpm-ostree-toolbox FWIW.

If you don't want a kernel, see the new container = true flag in rpm-ostree.

If you want to make docker images using rpm-ostree, stay tuned =)

[chrisruffalo]

I guess I'm confused as to how to initiate a tree then? I thought I had to use the treecompose command from the toolbox. I guess then I'm not sure how setting container = true will help.

If you want to make docker images using rpm-ostree, stay tuned =)

That's great news!