[elbe-devel] Problems creating file system

Wed May 11 13:24:21 CEST 2022

Hi,

Am 11.05.22 um 07:49 schrieb Müller, Steffen - LT:
> Good morning,
> 
> We are trying to build a debian root file system for our embedded Linux project.
> 
> Elbe seems the correct tool for us, but we have some problems.
> 
> We set up an Debian 11 on a Virtual Box machine and installed elbe.
> 
> When we now try to generate a file system we get the following error messages:
> 
> elbe initvm submit armhf-ti-beaglebone-black.xml
> 
> I: Configuring gpg-wks-server...
> 
> I: Configuring g++-8...
> 
> I: Configuring gpg-wks-client...
> 
> I: Configuring dpkg-dev...
> 
> I: Configuring liberror-perl...
> 
> I: Configuring git...
> 
> I: Configuring g++...
> 
> I: Configuring gnupg...
> 
> I: Configuring build-essential...
> 
> I: Configuring libc-bin...
> 
> I: Base system installed successfully.
> 
> I: debootstrap finished
> 
> I: copying local configuration
> 
> W: No local /etc/mailname to copy, relying on /var/cache/pbuilder/build/31224/etc/mailname to be correct
> 
> I: Installing apt-lines
> 
> I: Copy  /var/cache/elbe/6955311d-0298-4984-9302-f1c023d534bd/aptconfdir/apt.conf.d  to chroot
> 
> I: user script /var/cache/pbuilder/build/31224/tmp/hooks/G10elbe_apt_sources starting
> 
> Warning: apt-key output should not be parsed (stdout is not a terminal)
> 
> gpg: can't connect to the agent: IPC connect call failed
> 
> Err:1 http://127.0.0.1:8080/var/cache/elbe/6955311d-0298-4984-9302-f1c023d534bd/repo 
> <http://127.0.0.1:8080/var/cache/elbe/6955311d-0298-4984-9302-f1c023d534bd/repo> buster InRelease
> 
> Could not connect to 127.0.0.1:8080 (127.0.0.1). - connect (111: Connection refused)
> 
> Hit:2 http://ftp.de.debian.org/debian <http://ftp.de.debian.org/debian> buster InRelease
> 
> Get:3 http://security.debian.org <http://security.debian.org> buster/updates InRelease [65.4 kB]
> 
> The Connection refused message will be repeated a few times. We also get problems in generating hard links.
> 
> The Process ends with this message:
> 
> [CMD] rm -rf "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pdebuilder"
> 
> [CMD] rm -rf "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pbuilder/result" 
> "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pbuilder_cross/result"
> 
> [CMD] mkdir -p "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pbuilder/result"
> 
> [INFO] Retrieve pbuild sources: zlib
> 
> [CMD] cd "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pdebuilder";apt-get source --yes -q --download-only "zlib"
> 
> Reading package lists...
> 
> Need to get 397 kB of source archives.
> 
> Get:1 http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security/main 
> zlib 1:1.2.11.dfsg-2+deb11u1 (dsc) [2,905 B]
> 
> Get:2 http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security/main 
> zlib 1:1.2.11.dfsg-2+deb11u1 (tar) [370 kB]
> 
> Err:3 http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security/main 
> zlib 1:1.2.11.dfsg-2+deb11u1 (diff)
> 
>    Bad header line Bad header data [IP: 199.232.138.132 80]
> 
> Fetched 373 kB in 7s (56.4 kB/s)
> 
> W: Download is performed unsandboxed as root as file 'zlib_1.2.11.dfsg-2+deb11u1.dsc' couldn't be accessed by user 
> '_apt'. - pkgAcquire::Run (13: Permission denied)
> 
> E: Failed to fetch 
> http://security.debian.org/debian-security/pool/updates/main/z/zlib/zlib_1.2.11.dfsg-2%2bdeb11u1.debian.tar.xz 
> <http://security.debian.org/debian-security/pool/updates/main/z/zlib/zlib_1.2.11.dfsg-2%2bdeb11u1.debian.tar.xz>  Bad 
> header line Bad header data [IP: 199.232.138.132 80]
> 
> E: Failed to fetch some archives.
> 
> [ERROR] Build failed
> 
> Traceback (most recent call last):
> 
>    File "/usr/lib/python3/dist-packages/elbepack/asyncworker.py", line 183, in execute
> 
>      self.project.build(skip_pkglist=False,
> 
>    File "/usr/lib/python3/dist-packages/elbepack/elbeproject.py", line 577, in build
> 
>      self.pbuild(p)
> 
>    File "/usr/lib/python3/dist-packages/elbepack/elbeproject.py", line 442, in pbuild
> 
>      do('cd "%s";apt-get source %s "%s"' % (pdb_path, apt_args, src_uri))
> 
>    File "/usr/lib/python3/dist-packages/elbepack/shellhelper.py", line 258, in do
> 
>      raise CommandError(cmd, p.returncode)
> 
> elbepack.shellhelper.CommandError: Error: 100 returned from Command cd 
> "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f/pdebuilder";apt-get source --yes -q --download-only "zlib"
> 
> Project build was not successful, current status: build_failed
> 
> elbe control wait_busy Failed
> 
> The project will not be deleted from the initvm.
> 
> The files, that have been built, can be downloaded using:
> 
> /usr/bin/elbe control get_files --output "None" "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f"
> 
> The project can then be removed using:
> 
> /usr/bin/elbe control del_project "/var/cache/elbe/1428276e-456f-407a-98d4-d9ae3f31349f"
> 
> If we try to build the am64 examle we get the following output:
> 
> elbe initvm submit arm64-qemu-virt.xml
> 
> Build started, waiting till it finishes
> 
> [INFO] Build started
> 
> [INFO] ELBE Report for Project aarch64
> 
> Report timestamp: 20220510-091248
> 
> [ERROR] Build failed
> 
> Traceback (most recent call last):
> 
>    File "/usr/lib/python3/dist-packages/elbepack/asyncworker.py", line 183, in execute
> 
>      self.project.build(skip_pkglist=False,
> 
>    File "/usr/lib/python3/dist-packages/elbepack/elbeproject.py", line 570, in build
> 
>      self.xml.validate_apt_sources(m, self.arch)
> 
>    File "/usr/lib/python3/dist-packages/elbepack/elbexml.py", line 354, in validate_apt_sources
> 
>      raise ValidationError(
> 
> elbepack.elbexml.ValidationError: Repository http://ftp.de.debian.org/debian/dists/bullseye/ 
> <http://ftp.de.debian.org/debian/dists/bullseye/>, main/binary-arm64/Packages can not be validated
> 
> Project build was not successful, current status: build_failed
> 
> elbe control wait_busy Failed
> 
> The project will not be deleted from the initvm.
> 
> The files, that have been built, can be downloaded using:
> 
> /usr/bin/elbe control get_files --output "None" "/var/cache/elbe/de5f405f-c1ce-4bd4-b1b8-1fbe1706bda9"
> 
> The project can then be removed using:
> 
> /usr/bin/elbe control del_project "/var/cache/elbe/de5f405f-c1ce-4bd4-b1b8-1fbe1706bda9"
> 
> Do you possibly have an idea what we are doing wrong?
> 
> Our company uses a proxy server. We added this server address in the command line.

My first guess: the proxy configuration or the virtual network provided by VirtualBox is the problem.
Are you able to access the repositories from within the initvm (elbe initvm attach; then wget on a file)?

How do you provide the proxy info? Does it involve authentication?

> 
> Thanks for your support.
> 
> Regards
> 
> Steffen Müller
> 
> Informationen über den Umfang der Verarbeitung Ihrer personenbezogenen Daten und über Ihre Datenschutzrechte finden Sie hier:
> Information on the scope of the processing of your personal data and your data protection rights you find here:
> https://northropgrumman.litef.com/fileadmin/downloads/Pflichtinformationen-Artikel-13-DSGVO.pdf
> __________________________________________________________________________________________
> 
> Northrop Grumman LITEF GmbH ~ Amtsgericht Freiburg, HRB 3115 ~ Geschaeftsfuehrung: Lutz Kampmann ~ Vorsitzender des Aufsichtsrates: David Martin ~ Deutsche Bank Freiburg (BLZ 680 700 30) Account: 375 048 00,IBAN: DE96 6807 0030 0037 5048 00, BIC/SWIFT: DEUTDE6FXXX