Re: Few Fedora 20 ProjectAtomic VM questions

[Andy Grimm <agrimm gmail com>]

On Wed, Jun 11, 2014 at 12:51 PM, Adam Miller
<maxamillion fedoraproject org> wrote:
>
>
>
> On Wed, Jun 11, 2014 at 11:41 AM, Colin Walters <walters verbum org> wrote:
>>
>> Hi,
>>
>> On Wed, Jun 11, 2014, at 09:30 AM, Adam Miller wrote:
>>
>> Hello all,
>>     I've been working with the Fedora 20 image from projectatomic.io for
>> the past few days off and on in preparation for a presentation I'm
>> giving on Friday and I had a few questions that popped up.
>>
>> 1) For the command 'ostree log REFSPEC', where do I find out what it
>> wants as a REFSPEC?
>>
>>
>> ostree refs
>>
>>
>>
>> I tried a number of combinations of the output from 'ostree admin
>> status' but nothing I try seems to not error.
>>
>>
>> Hm, that should work.  What exactly did you run?
>
>
>
> Only ones I remember off hand were:
>
> -bash-4.2# ostree admin status
> * project-atomic-controller
> 6b6b1362241f1c658b54797b51c2215e32b0978f2201eeb7cd2068276adb9015.0
>     origin refspec:
> project-atomic-controller:project-atomic-controller/fc20/x86_64/buildmaster/controller/docker
>   project-atomic-controller
> afc1794b4b42df77edf1988897b167573b99e299fa39a15b07b235a0e7387d02.0
>     origin refspec:
> project-atomic-controller:project-atomic-controller/fc20/x86_64/buildmaster/controller/docker
> -bash-4.2# ostree log
> 6b6b1362241f1c658b54797b51c2215e32b0978f2201eeb7cd2068276adb9015.0
> error: Refspec
> '6b6b1362241f1c658b54797b51c2215e32b0978f2201eeb7cd2068276adb9015.0' not
> found
>
> -bash-4.2# ostree log
> project-atomic-controller:project-atomic-controller/fc20/x86_64/buildmaster/controller/docker
> commit 6b6b1362241f1c658b54797b51c2215e32b0978f2201eeb7cd2068276adb9015
> Date:  2014-06-09 22:34:26 +0000
>
>
> error: No such metadata object
> 0a5d57658b9324b5ff3ee7b1ac94913c4ff3ae5288d00c68980525932621f144.commit
> -bash-4.2# ostree log project-atomic-controller
> error: Couldn't open ref
> '/ostree/repo/refs/remotes/project-atomic-controller': Can't open directory

I didn't get this message, but got a similarly disappointing one (from
the 20140609 image):  "error: No such metadata object: ...."  I assume
that if you fix the problem with your broken remote, you'll see this
message next.  This is my (possibly incorrect) interpretation:  when
an atomic image is built, it doesn't contain the whole commit history
(as that would be quite large).  "ostree log" tries to track back
through the latest commit's ancestors, but it can only see commits
that you've pulled in since creating this instance.  Rather than
simply exiting or saying "I don't have a local copy of any ancestors
beyond this point" in some nice way, it barfs an error.  Not exactly
user-friendly, but it does make sense.

--Andy

> -AdamM
>
>>
>>
>>
>> 2) Does the latest version of the Fedora 20 projectatomic.io VM support
>> installing packages "on top" (for lack of a better phrasing) using yum?
>> Or is that still in the pipeline?
>>
>>
>> Still in the pipeline.
>>
>>
>>
>> 3) I'm curious about the output from findmnt, I'm seeing entries where
>> the source is /dev/vda3[some_stuff_in_brackets], I'm not familiar with
>> what that is or where it comes from and was hoping someone could provide
>> clarification.
>>
>>
>> Those are bind mounts.  There are a few of them.
>>
>> * /sysroot points to the physical root.
>> * /var is a bind mount outside the deployment root to the shared /var.
>> * /usr is a read-only bind mount for a few reasons, but the primary one
>>    is to avoid admins accidentally corrupting the object store (hardlink
>> farm)
>>
>>
>> I'm sure I'll come up with more questions in the future and would like
>> to apologize if this is line noise, but also offer some preliminary
>> gratitude to whom ever has answers.
>>
>>
>> No worries, we're still very much spinning up on the docs side.
>
>