fedora-iot kickstart - how to install additional packages

[Andrea Battaglia]

Hi all,

I'm reaching out to ask for help with the build of a custom Fedora IoT
image.

Starting from the official kickstart file:
*https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks
<https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks>*

I added several actions in the *%post* section to automate the manual
customization process.
All the changes are applied to the final image but one: the installation of
a new package, not included in the standard set.
Specifically, I'm trying to install the *i2c-tools* package.

Following the official guide, tried the followings
 - list the package name in the dedicated *%package* section: no effect
 - add the command *rpm-ostree install i2c-tools in the* %post section: no
effect.

In both cases, I test the final image on my RPi 3B+ running the command
*i2cdetect -l -a*
with the result
*-bash: i2cdetect: command not found*

Please find attached the files used in the build process.

Could you please provide some guidance?

Thanks a lot in advance,

Andrea

[Peter Robinson]

On Sat, Mar 27, 2021 at 10:14 AM Andrea Battaglia
<a.battaglia79(a)gmail.com&gt; wrote:
>  Hi all,
>
>  I'm reaching out to ask for help with the build of a custom Fedora IoT image.
>
>  Starting from the official kickstart file:
>  https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks
>
>  I added several actions in the %post section to automate the manual customization
> process.
>  All the changes are applied to the final image but one: the installation of a new
> package, not included in the standard set.
>  Specifically, I'm trying to install the i2c-tools package.
>
>  Following the official guide, tried the followings
>   - list the package name in the dedicated %package section: no effect 
There would be no effect, from that PoV you need to add it when the
ostree is created.

>   - add the command rpm-ostree install i2c-tools in the %post section:
> no effect. 
I would expect that option to work. I've not tried anything around
that in the ks. Does it work if you install it on the running image?

> In both cases, I test the final image on my RPi 3B+ running the command
> i2cdetect -l -a
> with the result
> -bash: i2cdetect: command not found
>
> Please find attached the files used in the build process.
>
> Could you please provide some guidance?
>
> Thanks a lot in advance,
>
> Andrea
>
> _______________________________________________
> IoT mailing list -- iot(a)lists.fedoraproject.org
> To unsubscribe send an email to iot-leave(a)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/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Andrea Battaglia]

Hi Peter,

yes, the command *rpm-ostree install i2c-tools* works as expected on the
running image.

Andrea

On Sat, Mar 27, 2021 at 12:42 PM Peter Robinson <pbrobinson(a)gmail.com&gt;
wrote:

>  On Sat, Mar 27, 2021 at 10:14 AM Andrea Battaglia
>  <a.battaglia79(a)gmail.com&gt; wrote:
>  >
>  > Hi all,
>  >
>  > I'm reaching out to ask for help with the build of a custom Fedora IoT
>  image.
>  >
>  > Starting from the official kickstart file:
>  > https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks
>  >
>  > I added several actions in the %post section to automate the manual
>  customization process.
>  > All the changes are applied to the final image but one: the installation
>  of a new package, not included in the standard set.
>  > Specifically, I'm trying to install the i2c-tools package.
>  >
>  > Following the official guide, tried the followings
>  >  - list the package name in the dedicated %package section: no effect
>
>  There would be no effect, from that PoV you need to add it when the
>  ostree is created.
>
>  >  - add the command rpm-ostree install i2c-tools in the %post section: no
>  effect.
>
>  I would expect that option to work. I've not tried anything around
>  that in the ks. Does it work if you install it on the running image?
>
>  > In both cases, I test the final image on my RPi 3B+ running the command
>  > i2cdetect -l -a
>  > with the result
>  > -bash: i2cdetect: command not found
>  >
>  > Please find attached the files used in the build process.
>  >
>  > Could you please provide some guidance?
>  >
>  > Thanks a lot in advance,
>  >
>  > Andrea
>  >
>  > _______________________________________________
>  > IoT mailing list -- iot(a)lists.fedoraproject.org
>  > To unsubscribe send an email to iot-leave(a)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/[e-mail]
>  > Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  _______________________________________________
>  IoT mailing list -- iot(a)lists.fedoraproject.org
>  To unsubscribe send an email to iot-leave(a)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/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Ben Breard]

Yeah, unfortunately this is a known limitation in the intersection of
rpm-ostree and anaconda. Silverblue has the same problem.




-Ben
Sent from Android device.

On Sat, Mar 27, 2021, 9:23 AM Andrea Battaglia <a.battaglia79(a)gmail.com&gt;
wrote:

>  Hi Peter,
>
>  yes, the command *rpm-ostree install i2c-tools* works as expected on the
>  running image.
>
>  Andrea
>
>  On Sat, Mar 27, 2021 at 12:42 PM Peter Robinson <pbrobinson(a)gmail.com&gt;
>  wrote:
>
> > On Sat, Mar 27, 2021 at 10:14 AM Andrea Battaglia
> > <a.battaglia79(a)gmail.com&gt; wrote:
> > >
> > > Hi all,
> > >
> > > I'm reaching out to ask for help with the build of a custom Fedora IoT
> > image.
> > >
> > > Starting from the official kickstart file:
> > > https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks
> > >
> > > I added several actions in the %post section to automate the manual
> > customization process.
> > > All the changes are applied to the final image but one: the
> > installation of a new package, not included in the standard set.
> > > Specifically, I'm trying to install the i2c-tools package.
> > >
> > > Following the official guide, tried the followings
> > >  - list the package name in the dedicated %package section: no effect
> >
> > There would be no effect, from that PoV you need to add it when the
> > ostree is created.
> >
> > >  - add the command rpm-ostree install i2c-tools in the %post section:
> > no effect.
> >
> > I would expect that option to work. I've not tried anything around
> > that in the ks. Does it work if you install it on the running image?
> >
> > > In both cases, I test the final image on my RPi 3B+ running the command
> > > i2cdetect -l -a
> > > with the result
> > > -bash: i2cdetect: command not found
> > >
> > > Please find attached the files used in the build process.
> > >
> > > Could you please provide some guidance?
> > >
> > > Thanks a lot in advance,
> > >
> > > Andrea
> > >
> > > _______________________________________________
> > > IoT mailing list -- iot(a)lists.fedoraproject.org
> > > To unsubscribe send an email to iot-leave(a)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/[e-mail]
> > > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> > _______________________________________________
> > IoT mailing list -- iot(a)lists.fedoraproject.org
> > To unsubscribe send an email to iot-leave(a)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/[e-mail]
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> >
>  _______________________________________________
>  IoT mailing list -- iot(a)lists.fedoraproject.org
>  To unsubscribe send an email to iot-leave(a)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/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>

[Andrea Battaglia]

Hi Ben,

That’s definitely unfortunate.

Is there a way to automate the build process without anaconda? 

Happy to help testing different options/methods.

Andrea



>  On 27 Mar 2021, at 18:03, Ben Breard <mrguitar.net(a)gmail.com&gt;
> wrote:
>  
>  
>  Yeah, unfortunately this is a known limitation in the intersection of rpm-ostree and
> anaconda. Silverblue has the same problem. 
>  
>  
>  
>  
>  -Ben
>  Sent from Android device.
>  
> > On Sat, Mar 27, 2021, 9:23 AM Andrea Battaglia <a.battaglia79(a)gmail.com&gt;
> wrote:
> > Hi Peter,
> > 
> > yes, the command rpm-ostree install i2c-tools works as expected on the running
> image.
> > 
> > Andrea
> > 
> >> On Sat, Mar 27, 2021 at 12:42 PM Peter Robinson <pbrobinson(a)gmail.com&gt;
> wrote:
> >> On Sat, Mar 27, 2021 at 10:14 AM Andrea Battaglia
> >> <a.battaglia79(a)gmail.com&gt; wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I'm reaching out to ask for help with the build of a custom Fedora IoT
> image.
> >> >
> >> > Starting from the official kickstart file:
> >> > https://pagure.io/fedora-kickstarts/blob/f33/f/fedora-iot.ks
> >> >
> >> > I added several actions in the %post section to automate the manual
> customization process.
> >> > All the changes are applied to the final image but one: the installation of
> a new package, not included in the standard set.
> >> > Specifically, I'm trying to install the i2c-tools package.
> >> >
> >> > Following the official guide, tried the followings
> >> >  - list the package name in the dedicated %package section: no effect
> >> 
> >> There would be no effect, from that PoV you need to add it when the
> >> ostree is created.
> >> 
> >> >  - add the command rpm-ostree install i2c-tools in the %post section: no
> effect.
> >> 
> >> I would expect that option to work. I've not tried anything around
> >> that in the ks. Does it work if you install it on the running image?
> >> 
> >> > In both cases, I test the final image on my RPi 3B+ running the command
> >> > i2cdetect -l -a
> >> > with the result
> >> > -bash: i2cdetect: command not found
> >> >
> >> > Please find attached the files used in the build process.
> >> >
> >> > Could you please provide some guidance?
> >> >
> >> > Thanks a lot in advance,
> >> >
> >> > Andrea
> >> >
> >> > _______________________________________________
> >> > IoT mailing list -- iot(a)lists.fedoraproject.org
> >> > To unsubscribe send an email to iot-leave(a)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/[e-mail]
> >> > Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
> >> _______________________________________________
> >> IoT mailing list -- iot(a)lists.fedoraproject.org
> >> To unsubscribe send an email to iot-leave(a)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/[e-mail]
> >> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
> > _______________________________________________
> > IoT mailing list -- iot(a)lists.fedoraproject.org
> > To unsubscribe send an email to iot-leave(a)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/[e-mail]
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>  _______________________________________________
>  IoT mailing list -- iot(a)lists.fedoraproject.org
>  To unsubscribe send an email to iot-leave(a)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/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure