[fedora-arm] Re: Building fedora-arm images

2020-04-01 Thread Fabrizio D'Angelo 

Hi Martin,

Thanks for your response.
Yesterday I got in touch with Ondřej from the osbuild-composer team (CC).
He helped me switch over from Lorax to osbuild and I was able to get an 
aarch64 image built with it.
You are most likely correct about the RPi images being a bit special 
since the image produced did not boot properly on my RPi.


I have just tried out plain osbuild as you suggested and opened a new issue.

osbuild seems like it could be very useful for us.
I would like to help get RPi builds working successfully with it, please 
let me know if I can help. I can help test builds at the very least.



Thank you,

Fabrizio




On 4/1/20 3:08 AM, Martin Sehnoutka wrote:


 > Is there anyone on this list that has that information or knows where 
 > I could find it?


Hi,

I work on a project that is basically a replacement to Lorax which 
you've already tried. The whole project is called OSBuild:
https://urldefense.com/v3/__https://github.com/osbuild__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee0JuRyICw$ 
and it consists of two parts. One is a low level CLI tool which you can 
use to produce images described by a JSON file:
https://urldefense.com/v3/__https://github.com/osbuild/osbuild/tree/master/samples__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee00DD1KgA$ 
and the second part is an HTTP service just like Lorax that you can use 
with your blueprints:
https://urldefense.com/v3/__https://github.com/osbuild/osbuild-composer__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee2AsmIxNw$ 
The difference from Lorax is that osbuild-composer will produce the JSON 
file I mentioned above and it will call osbuild.


Both are packaged in Fedora:
https://urldefense.com/v3/__https://src.fedoraproject.org/rpms/osbuild__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee0J4-qfPA$ 
https://urldefense.com/v3/__https://src.fedoraproject.org/rpms/golang-github-osbuild-composer__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee0Af3nKpQ$ 
and the second one will soon be replaced by less confusing name:
https://urldefense.com/v3/__https://src.fedoraproject.org/rpms/osbuild-composer__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee1uvPw9Rw$ 
but the content of the packages should be the same at this point.


I'd, personally, recommend you to take a look at plain osbuild 
(https://urldefense.com/v3/__https://github.com/osbuild/osbuild__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee1LyEDaxw$ 
) and ask questions in a Github issue.


Support for aarch64 in osbuild-composer should hopefully land soon, but 
if I remember correctly RPi images are somewhat special so even once we 
have support for aarch64 we would still need to make sure it works on RPi.


Hope you find osbuild useful and feel free to ask questions.
Martin
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://urldefense.com/v3/__https://docs.fedoraproject.org/en-US/project/code-of-conduct/__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee2y99WY6A$ 
List Guidelines: 
https://urldefense.com/v3/__https://fedoraproject.org/wiki/Mailing_list_guidelines__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee0ohjlEPw$ 
List Archives: 
https://urldefense.com/v3/__https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org__;!!IrdRlI43zQ!ORXj3tyeImuKmUXn3PLLTh0JjjINbCDbXeVm22t4f8IuqLzf-xxIbcOnDacedVWuipi5Ee2Fb5eCgg$ 


___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[fedora-arm] Re: Building fedora-arm images

2020-04-01 Thread Martin Sehnoutka 


> Is there anyone on this list that has that information or knows where 
> I could find it?


Hi,

I work on a project that is basically a replacement to Lorax which 
you've already tried. The whole project is called OSBuild:

https://github.com/osbuild
and it consists of two parts. One is a low level CLI tool which you can 
use to produce images described by a JSON file:

https://github.com/osbuild/osbuild/tree/master/samples
and the second part is an HTTP service just like Lorax that you can use 
with your blueprints:

https://github.com/osbuild/osbuild-composer
The difference from Lorax is that osbuild-composer will produce the JSON 
file I mentioned above and it will call osbuild.


Both are packaged in Fedora:
https://src.fedoraproject.org/rpms/osbuild
https://src.fedoraproject.org/rpms/golang-github-osbuild-composer
and the second one will soon be replaced by less confusing name:
https://src.fedoraproject.org/rpms/osbuild-composer
but the content of the packages should be the same at this point.

I'd, personally, recommend you to take a look at plain osbuild 
(https://github.com/osbuild/osbuild) and ask questions in a Github issue.


Support for aarch64 in osbuild-composer should hopefully land soon, but 
if I remember correctly RPi images are somewhat special so even once we 
have support for aarch64 we would still need to make sure it works on RPi.


Hope you find osbuild useful and feel free to ask questions.
Martin
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[fedora-arm] Re: Building fedora-arm images

2020-03-30 Thread Mohan Boddu 
In Fedora we use both image factory and appliance creator. We use image factory 
which calls Oz to create disk images and appliance creator to build live 
images. We are building live images using appliance creator for only armhfp.

I never tried building it locally as I always used koji and built the images as 
part of testing.

> Any chance you have some input on the image-factory error: "Guest 
> disabled display"?
> Just kinda tries building for a while until it fails with only that 
> message outputted as an image.
> 
> 
> Thank you,
> 
> Fabrizio

AFAIR, I haven't seen this error. Have you looked in to oz log? Sometimes it 
has more information about the issue.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[fedora-arm] Re: Building fedora-arm images

2020-03-29 Thread Fabrizio D'Angelo 



On 3/29/20 1:24 PM, Matthew Miller wrote:


Maybe. I'll point the people working on the project at this and see what
they say.



I also tried taking a step back and building a more basic image with 
cockpit. I get this error with any blueprint I create as well as the 
example blueprints(I've tried to make both a raw image and .iso, same 
issue):


2020-03-29 13:33:48,266 ERROR: Running anaconda failed: process 
'['unshare', '--pid', '--kill-child', '--mount', '--propagation', 
'unchanged', 'anaconda', '--kickstart', 
'/var/lib/lorax/composer/results/3d6fdcc1-9632-4854-be87-b850ad865a8f/final-kickstart.ks', 
'--cmdline', '--loglevel', 'debug', '--dirinstall', '--remotelog', 
'127.0.0.1:33571']' exited with status 1

2020-03-29 13:34:41,512 INFO: Running... umount /mnt/sysimage
2020-03-29 13:34:41,710 DEBUG: Return code: 0
2020-03-29 13:34:41,711 ERROR: Install failed: novirt_install failed
2020-03-29 13:34:41,712 INFO: Removing bad disk image
2020-03-29 13:34:41,714 ERROR: ERROR: Image creation failed: 
novirt_install failed
2020-03-29 13:34:41,717 DEBUG: Install finished, chowning results to 
root:weldr

2020-03-29 13:34:41,732 ERROR: traceback: Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/pylorax/installer.py", line 
397, in novirt_install

callback=lambda p: not novirt_cancel_check(cancel_funcs, p)):
  File "/usr/lib/python3.7/site-packages/pylorax/executils.py", line 
317, in __next__

(self._argv, self._proc.returncode))
OSError: process '['unshare', '--pid', '--kill-child', '--mount', 
'--propagation', 'unchanged', 'anaconda', '--kickstart', 
'/var/lib/lorax/composer/results/3d6fdcc1-9632-4854-be87-b850ad865a8f/final-kickstart.ks', 
'--cmdline', '--loglevel', 'debug', '--dirinstall', '--remotelog', 
'127.0.0.1:33571']' exited with status 1


During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/pylorax/creator.py", line 669, 
in run_creator

disk_img = make_image(opts, ks, cancel_func=cancel_func)
  File "/usr/lib/python3.7/site-packages/pylorax/creator.py", line 478, 
in make_image
novirt_install(opts, disk_img, disk_size, cancel_func=cancel_func, 
tar_img=tar_img)
  File "/usr/lib/python3.7/site-packages/pylorax/installer.py", line 
424, in novirt_install

raise InstallError("novirt_install failed")
pylorax.installer.InstallError: novirt_install failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/pylorax/api/queue.py", line 
162, in monitor

make_compose(cfg, os.path.realpath(dst))
  File "/usr/lib/python3.7/site-packages/pylorax/api/queue.py", line 
267, in make_compose

run_creator(install_cfg, cancel_func=cancel_build)
  File "/usr/lib/python3.7/site-packages/pylorax/creator.py", line 672, 
in run_creator

raise RuntimeError("Image creation failed: %s" % e)
RuntimeError: Image creation failed: novirt_install failed


I haven't looked too deeply at this error yet, just thought I might as 
well share it.



I think "Installation Destination (Kickstart insufficient)" is a complaint
about something in the storage definition part of the kickstart file. Can
you post that part of the flattened ks file?


Sure thing:

# System bootloader configuration
bootloader --location=mbr
# Disk partitioning information
part /boot/efi --asprimary --fstype="vfat" --size=80
part /boot --asprimary --fstype="ext4" --size=512
part / --fstype="ext4" --size=1400


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


And the $1 in this case is a argument with the actual ks file, right? Just
checking :)



Correct :)



Any chance you have some input on the image-factory error: "Guest 
disabled display"?
Just kinda tries building for a while until it fails with only that 
message outputted as an image.



Thank you,

Fabrizio
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[fedora-arm] Re: Building fedora-arm images

2020-03-29 Thread Matthew Miller 
On Sat, Mar 28, 2020 at 11:46:19AM -0400, Fabrizio D'Angelo wrote:
> /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?

Maybe. I'll point the people working on the project at this and see what
they say.

> 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
> (Custom software selected)
> 2020-02-10 18:24:17,330: rg/mirrorlist?repo=rawhide=
> 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.
> I have also tried this with an added a user account, root password,
> and activated network. Same deal.

I think "Installation Destination (Kickstart insufficient)" is a complaint
about something in the storage definition part of the kickstart file. Can
you post that part of the flattened ks file?

> 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

And the $1 in this case is a argument with the actual ks file, right? Just
checking :)


-- 
Matthew Miller

Fedora Project Leader
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

[fedora-arm] Re: Building fedora-arm images

2020-03-28 Thread Fabrizio D'Angelo 


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 
> 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


(Custom software selected)
2020-02-10 18:24:17,330: rg/mirrorlist?repo=rawhide=
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

.
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:
 >
 >

[fedora-arm] Re: Building fedora-arm images

2020-03-28 Thread DancesWithCars 
Dumb question:
Are you cross compiling
Or trying to build on RPis?


On Sat, Mar 28, 2020, 11:46 Fabrizio D'Angelo <
fabrizio_dang...@student.uml.edu> 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
> (Custom software selected)
> 2020-02-10 18:24:17,330: rg/mirrorlist?repo=rawhide=
> 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.
> 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:
> >
> >
>

[fedora-arm] Re: Building fedora-arm images

2020-03-28 Thread Fabrizio D'Angelo 

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
(Custom software selected)
2020-02-10 18:24:17,330: rg/mirrorlist?repo=rawhide=
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.
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

[fedora-arm] Re: Building fedora-arm images

2020-03-27 Thread Matthew Miller 
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? 

> 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://pagure.io/pungi with config from https://pagure.io/pungi-fedora. You
can see Fedora-minimal-armhfp in the config here:

https://pagure.io/pungi-fedora/blob/master/f/fedora.conf

and that references 
https://pagure.io/fedora-kickstarts/blob/master/f/fedora-arm-minimal.ks

This fires off tasks like this one: 
https://koji.fedoraproject.org/koji/taskinfo?taskID=42795427

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://kojipkgs.fedoraproject.org//work/tasks/5428/42795428/mock_output.log



-- 
Matthew Miller

Fedora Project Leader
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
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@lists.fedoraproject.org