Re: Creating directory on / ?

[Leandro Santiago <leandrosansilva gmail com>]

I think I solved my problem in a very dirty way...

The workaround I am doing now is the following:

- build and commit a tree on a repo with rpm-ostree and putting the
commit checksum in CURRENT_COMMIT
- then
$ mkdir -p /tmp/underlay_root/rootfs
$ ostree commit --repo=$REPO --tree=dir=/tmp/underlay_root/rootfs
--tree=ref=$CURRENT_COMMIT --branch=$REF_NAME

It will merge the tree on $CURRENT_COMMIT with a tree with only the
directory I need to create.

Until a better solution comes up, I think it will be enough for me :-)

On 3 July 2015 at 10:25, Leandro Santiago <leandrosansilva gmail com> wrote:
> Oh, I am using the latest ostree and rpm-ostree versions from
> atomic7-testing repository.
>
> On 3 July 2015 at 08:52, Leandro Santiago <leandrosansilva gmail com> wrote:
> > Thanks, I tried that. Didn't work. I checked the generated rpm package
> > and it does have an empty /rootfs directory, but it's not present on
> > either system / or /ostree/<deploy dir>.
> >
> > Unfortunately in my case it's not possible to move my code to a docker
> > container, as they are a lot of small utilitaries which depend on the
> > host.
> >
> > Any clues about how to do it on dracut?
> >
> > About the directory structure, I checked out that those directories
> > paths are hardcoded. Wouldn't it be the case of adding something like
> > a field on tree.json with the extra paths, specifying if they are
> > manageable by ostree or not, etc.?
> >
> > On 2 July 2015 at 15:47, Colin Walters <walters verbum org> wrote:
> > > We would also need to teach rpm-ostree how to take other content
> > > besides jus
> >
> >
> >
> >
> > --
> > Sent from my mind
>
>
>
> --
> Sent from my mind



-- 
Sent from my mind