On 3/28/20 1:08 PM, DancesWithCars wrote:
Dumb question:
Are you cross compiling
Or trying to build on RPis?
Building on an aarch64 APM Mustang server.
By the way, that imagefactory ended up failing.
Generated a screenshot as an error message that just said "Guest
disabled display"
I'm looking into ways to deal with that, but we ran into this issue on
the last build server and did not find a solution.
On Sat, Mar 28, 2020, 11:46 Fabrizio D'Angelo
<fabrizio_dangelo@xxxxxxxxxxxxxxx
<mailto:fabrizio_dangelo@xxxxxxxxxxxxxxx>> wrote:
Hi Matthew,
Thanks so much for the reply.
On 3/27/20 6:16 PM, Matthew Miller wrote:
> On Fri, Mar 27, 2020 at 03:28:34PM -0400, Fabrizio D'Angelo wrote:
>> We've tried image-factory, livemedia-creator, appliance-tools, oz...
>> No luck with anything yet.
>
> What problems are you running into? Did the image builder in
Cockpit get you
> anywhere?
>
Cockpit seems like it could be useful for us. Just maybe need a few
pointers with it.
The blueprints seem to create a .toml file in
/var/lib/lorax/composer/blueprints/git/workspace/master/
The UI for Cockpit is great, but I can't find an option for adding in
several packages at once. To avoid having to search and add each
individual package, I used a script to add to the .toml file for the
blueprint in the same format as the ones that got input by Cockpit.
Like so:
[[packages]]
name = "dejavu-sans-fonts"
version = "*"
After doing this, Cockpit just won't load blueprints anymore.
Perhaps there's a better way to go about this?
With appliance-tools we were able to build images, but they did not
boot. We didn't have a serial cable to debug with at the time, but
shortly after, we found out that building aarch64 images was not
supported.
The closest we've gotten to success was with livemedia-creator.
Here is the anaconda output of the error I got hung up on:
2020-02-10 18:24:17,327: 1) [x] Language settings 2)
[x] Time settings
2020-02-10 18:24:17,328: (English (United States)) (America/New_York
timezone)
2020-02-10 18:24:17,329: 3) [x] Installation source 4)[x]
Software selection
2020-02-10 18:24:17,329: (https://mirrors.fedoraproject.o
<https://urldefense.com/v3/__https://mirrors.fedoraproject.o__;!!IrdRlI43zQ!ItsXq4C5hnoZsTOHS6Zl851oqMRfCaPTd45p2GPpLMh2JxJmVWukBLbfAbTJKRuwDdjj8ywy-JwY3g$>
(Custom software selected)
2020-02-10 18:24:17,330: rg/mirrorlist?repo=rawhide&arch=
2020-02-10 18:24:17,330: $basearch)
2020-02-10 18:24:17,331: 5) [!] Installation Destination
2020-02-10 18:24:17,331: (Kickstart insufficient)
The kickstart I used was exactly the result from using
ksflatten on fedora-arm-minimal.ks from
https://pagure.io/fedora-kickstarts
<https://urldefense.com/v3/__https://pagure.io/fedora-kickstarts__;!!IrdRlI43zQ!ItsXq4C5hnoZsTOHS6Zl851oqMRfCaPTd45p2GPpLMh2JxJmVWukBLbfAbTJKRuwDdjj8ywUcgLZkQ$>.
I have also tried this with an added a user account, root password, and
activated network. Same deal.
I used the following command to attempt to create the image:
livemedia-creator --make-disk --ks $1 --image-only --no-virt
--resultdir /home/rpi/build/image --releasever 30 --image-name
Fedora30BuildTEST
We weren't able to get much information about this error. From reading
forums, we found that sometimes it's about the way disk partitioning is
set up on the ks file. Played around with that, but did not move on
from
that error.
I'm giving image-factory another go right now since I recently finished
setting up a new build server. An issue we were dealing with before was
the lack of support for nested virtualization on aarch64. (We had
one of
those Mustang boards running CentOS with a very picky serial port, so
installing Fedora on it was a bit hard) That led us to try
livemedia-creator because of the "no-virt" option.
It seems I actually have an image building with image-factory right now.
Probably going to be an hour or two before it finishes, so I'll see how
it goes.
>> I'm sure there is some known combination of scripts/programs,
>> hardware, and operating system that was used to produce the
>> Fedora-Minimal images we've been working from.
>
> It's kind of a rube goldberg machine in its complexity. The
images are
> produced as part of the Fedora compose. This is orchestrated by
Pungi --
>
https://urldefense.com/v3/__https://pagure.io/pungi__;!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtNOembVLQ$
with config from
https://urldefense.com/v3/__https://pagure.io/pungi-fedora__;!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtO3TEszlg$
. You
> can see Fedora-minimal-armhfp in the config here:
>
>
https://urldefense.com/v3/__https://pagure.io/pungi-fedora/blob/master/f/fedora.conf__;!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtP5OuqVxg$
>
> and that references
https://urldefense.com/v3/__https://pagure.io/fedora-kickstarts/blob/master/f/fedora-arm-minimal.ks__;!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtOZEK_q_A$
>
> This fires off tasks like this one:
https://urldefense.com/v3/__https://koji.fedoraproject.org/koji/taskinfo?taskID=42795427__;!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtPqfZIpnA$
>
> Looks like this is (to my surprise, but I guess not great
surprise) still
> using the venerable "appliance-creator" tool. From the task
above, you can
> see how this is called:
>
>
https://urldefense.com/v3/__https://kojipkgs.fedoraproject.org/*work/tasks/5428/42795428/mock_output.log__;Lw!!IrdRlI43zQ!Nxv4gbCZ66JtKsKVdb4cZCFNbwNeO1YAVhH96soOidRcKnsKbjqWD6s6e8_co3-dbXmPxtOyjSG9hA$
Thanks a lot for this. I wanted to avoid reinventing a rube goldberg
machine so this will be a good resource for me.
Thanks again,
Fabrizio
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:arm@xxxxxxxxxxxxxxxxxxxxxxx>
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:arm-leave@xxxxxxxxxxxxxxxxxxxxxxx>
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
<https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/project/code-of-conduct/__;!!IrdRlI43zQ!ItsXq4C5hnoZsTOHS6Zl851oqMRfCaPTd45p2GPpLMh2JxJmVWukBLbfAbTJKRuwDdjj8yxI3Dtz2g$>
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
<https://urldefense.com/v3/__https://fedoraproject.org/wiki/Mailing_list_guidelines__;!!IrdRlI43zQ!ItsXq4C5hnoZsTOHS6Zl851oqMRfCaPTd45p2GPpLMh2JxJmVWukBLbfAbTJKRuwDdjj8yymhr3ctw$>
List Archives:
https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
<https://urldefense.com/v3/__https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org__;!!IrdRlI43zQ!ItsXq4C5hnoZsTOHS6Zl851oqMRfCaPTd45p2GPpLMh2JxJmVWukBLbfAbTJKRuwDdjj8yzm5dge3g$>
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
