BalenaOS Builds failing on Fedora 32

Hi,
I just upgraded to fedora 32 from fedora 31 yesterday and it seems like that somehow broke the build environment. I am curious because afaik balenaos builds inside a docker container so changes to host os shouldn’t matter, right?

The error is this:

ERROR: Task (virtual:native:/mnt/aosp/YOCTO/balena/balena-intel/build/../layers/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_compile) failed with exit code '1'

Log attatched.build.log (70.3 KB)

Hi @ric96 - thanks for posting this. We have not seen this error before. It would be good to get a bit more info about your environment, and how you’re encountering this:

  • Is this a fresh installation of Fedora 32, or did you upgrade in-place?
  • Can you post the command you run to kick off the build?
  • What architecture/device are you building for, and what architecture/device are you building on?
  • Are you able to show the versions of the docker images you’re using for the build? (I’m wondering if it’s possible that you downloaded a fresh Docker image after the upgrade to Fedora 32.)

All the best,
Hugh

Hi @saintaardvark

Is this a fresh installation of Fedora 32, or did you upgrade in-place?

Upgraded from fedora 31, last sane build environment.

Can you post the command you run to kick off the build?

./balena-yocto-scripts/build/barys -m genericx86-64-ext

What architecture/device are you building for, and what architecture/device are you building on?

X86_x64 to x86_64 and x86_64 to aarch64. both have the same issue

Are you able to show the versions of the docker images you’re using for the build?

[sahaj@fedora-work balena-intel]$ docker image ls
REPOSITORY                   TAG                 IMAGE ID            CREATED             SIZE
<none>                       <none>              2bc537c65b13        5 days ago          277MB
<none>                       <none>              418d5f67d42a        5 days ago          276MB
docker-disk-3088             latest              c09424c22e77        5 days ago          175MB
docker-disk-4119             latest              c09424c22e77        5 days ago          175MB
docker-disk-7093             latest              c09424c22e77        5 days ago          175MB
docker-disk-11332            latest              c09424c22e77        5 days ago          175MB
docker-disk-19457            latest              c09424c22e77        5 days ago          175MB
docker-disk-24195            latest              c09424c22e77        5 days ago          175MB
<none>                       <none>              acefd985513f        5 days ago          855MB
debian                       stretch             bd753a4a335e        6 days ago          101MB
balenalib/intel-nuc-debian   stretch-20190717    6d11514990a5        7 months ago        142MB
docker                       18.06-dind          79665797cba5        11 months ago       166MB
[sahaj@fedora-work balena-intel]$

Hi @ric96 , did you run this command from inside a container? Also I assume that you use this project right https://github.com/balena-os/balena-yocto-scripts ? In general I don’t see any docker commands in the script you run.

maybe because of this error I got when i run it inside a lxc container

000000002][LOG]BalenaOS build initialized in directory: build.
[000000002][LOG]Run build for genericx86-64-ext: MACHINE=genericx86-64-ext bitbake resin-image-flasher 
[000000002][LOG]This might take a while ...
ERROR: /home/ric/aosp_drive/balena-ub/balena-intel/build/../layers/meta-balena/meta-balena-common/recipes-containers/docker-disk/docker-disk.bb: docker-disk: Docker needs to run on your host and current user must be able to use it.
ERROR: Failed to parse recipe: /home/ric/aosp_drive/balena-ub/balena-intel/build/../layers/meta-balena/meta-balena-common/recipes-containers/docker-disk/docker-disk.bb

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
[000000006][LOG]Build for genericx86-64-ext failed. Check failed log in build/tmp/log/cooker/genericx86-64-ext .
[000000006][LOG]If build for genericx86-64-ext succeeded, final image should have been generated here:
[000000006][LOG]   build/tmp/deploy/images/genericx86-64-ext/resin-image-flasher-genericx86-64-ext.resinos-img
[000000006][LOG]Done.
ric@beech:~/aosp_drive/balena-ub/balena-intel$ 

as the error states:

Docker needs to run on your host and current user must be able to use it

is there a docker daemon accessible inside the lxc container?

@robertgzr it is now, i figured that out.

The original issue however was on a bare metal fedora 32 install, that was upgraded from a fedora 31 install. I need some help in figuring out what dependency broke.

Hi there, Fedora 32 does not appear to be a supported Yocto build distribution. Until Yocto updates support for this specific version, I am afraid it won’t work. It is also worth mentioning though that not all images can be built on Fedora (regardless of version) - anything that uses AUFS instead of OverlayFS will fail as AUFS is not in Fedora kernel.

Yes I’m aware of the AUFS issue, just using overlay for now.
I guess i’ll bring it up with yocto folks, for the time being builds are passing on my ubuntu lxc container so its not much of a dealbreaker.