Is anyone else having problems with 'rpm-ostree install' on aarch64
(rpi3) iot images?
It's working for me on x86_64, but not aarch64.
I don't know if my raspberry pi is messed up or maybe it's something else.
I'm getting the following
# rpm-ostree install nodejs-bindings
Checking out tree 8d33770... done
Enabled rpm-md repositories: updates-modular fedora updates fedora-modular
rpm-md repo 'updates-modular' (cached); generated: 2019-02-02T03:06:21Z
rpm-md repo 'fedora' (cached); generated: 2018-10-24T22:18:20Z
rpm-md repo 'updates' (cached); generated: 2019-02-04T12:55:48Z
rpm-md repo 'fedora-modular' (cached); generated: 2018-10-24T22:20:20Z
Importing metadata [=============] 100%
Resolving dependencies... done
Will download: 2 packages (11.9 MB)
Downloading from updates-modular: [=============] 100%
Importing (2/2) [=============] 100%
Checking out packages (5/5) [=============] 100%
Running pre scripts... 0 done
Running post scripts... error: Executing %transfiletriggerin for info:
Executing bwrap(/bin/sh): Child process killed by signal 7; run
`journalctl -t 'rpm-ostree(info.transfiletriggerin)'` for more
# journalctl -t 'rpm-ostree(info.transfiletriggerin)'-- Logs begin at
Mon 2018-10-29 00:29:01 UTC, end at Mon 2019-02-04 17:22:30 UTC. --
-- No entries --
This is on a fresh, non-updated f29-iot image 
If someone could just try to install something on aarch64 using
rpm-ostree and let me know if it's just me, or something is broken, I
would appreciate it.
 - Fedora-IoT-29-20181206.0.aarch64.raw.xz
I plan to be in the IRC meeting tomorrow but I don't want to fill the time
trying to type all this in...
I am working on expanding the Getting Started Guide .
Work in progress is being merged into a getting-started branch  which
despite the branch name, includes changes to the entire IoT docs site.
I am focusing the Getting Started docs on getting an image booted (VM or
Physical), with a user, and applying updates (even though there are not
currently any updates to apply). Other topics will be in a separate guide
I have added a placeholder for an "Obtaining Images" page which will
provide context and point to the not yet available iot.fedoraproject.org
I also have taken some of the the other small topics already on the site
and created a "User Guide" section. I see a number of ideas on the
SilverBlue pages  that could eventually be modified for IoT and added
here as well.
With the first PR, Peter made a side comment and wondered about also a
Silverblue just uses "Silverblue Guide" rather than calling it a User Guide
and it does have some topics ("Generating Your Own SilverBlue ISO" for
example) which could be considered developer rather than user. The Fedora
Docs site has a "Contributor Guide"  including how to build a local
So my first set of questions:
*Is there a significant difference in what a "user" vs "developer" would
need to know? (I hope that developers are also users!) If so, what would
those developer specific topic be?
*Would a contributor guide be more in line with topics not thought of as
user guide materials? It can have some of the more technical tasks needed
for self QA before a PR as well as other process information.
*What would you like to see as the title for a guide that has the "next
steps" beyond getting started? Leave my (admittedly administrator/user
biased) instinct to call it a "User Guide" or make it more general as "IoT
Guide"? (You may have different answers depending on the "all in one" vs
"multi" guides outcome.)
I plan to be in the IRC meeting tomorrow.
 based off https://iot.stg.fedoraproject.org/ but with working Verify
Susan Lauber, (CCAH, RHCX, RHCA, RHCSS, RHCVA, CISSP)
Lauber System Solutions, Inc.
gpg: 15AC F794 A3D9 64D1 D9CE 4C26 EFC3 11C2 BFA1 0974