In
the previous post,
I have shared my first experience with the Debian images builder -
debos. I have posted my current results on
the issue but since there was no
response, I’ve decided to try to move forward by myself.
Just to remind - I was stuck at the following error (when building for arm64):
1
2
3
4
5
6
7
8
9
10
11
12
2018/07/26 18:36:39 Debootstrap (stage 2) | chroot: failed to run command'/debootstrap/debootstrap': Exec format error
2018/07/26 18:36:39 debootstrap.log | gpgv: Signature made Thu Jul 26 14:21:51 2018 UTC
2018/07/26 18:36:39 debootstrap.log | gpgv: using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
2018/07/26 18:36:39 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) "
2018/07/26 18:36:39 debootstrap.log | gpgv: Signature made Thu Jul 26 14:21:51 2018 UTC
2018/07/26 18:36:39 debootstrap.log | gpgv: using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
2018/07/26 18:36:39 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) "
2018/07/26 18:36:39 debootstrap.log | gpgv: Signature made Thu Jul 26 14:21:51 2018 UTC
2018/07/26 18:36:39 debootstrap.log | gpgv: using RSA key 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC
2018/07/26 18:36:39 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (9/stretch) "
2018/07/26 18:36:39 Action `debootstrap` failed at stage Run, error: exit status 126
Powering off.
Potential solution
After some research, it seemed like the
binfmt_misc support might be
missing in my setup. Links with similar issues which were useful:
At first, it seemed to be necessary to install binfmt-support into the
docker image. It is necessary to note, that binfmt_misc module on the host
must be loaded (which is not always the case). With those modifications in
place, my debos build inside docker container failed at:
1
2
3
4
5
6
7
8
9
10
11
12
13
2018/08/21 19:17:06 Debootstrap (stage 2) | W: Failure trying to run: mount -t proc proc /proc
2018/08/21 19:17:06 Debootstrap (stage 2) | W: See //debootstrap/debootstrap.log for details
2018/08/21 19:17:06 debootstrap.log | gpgv: Signature made Tue Aug 21 14:20:20 2018 UTC
2018/08/21 19:17:06 debootstrap.log | gpgv: using RSA key A1BD8E9D78F7FE5C3E65D8AF8B48AD6246925553
2018/08/21 19:17:06 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (7.0/wheezy) <ftpmaster@debian.org>"
2018/08/21 19:17:06 debootstrap.log | gpgv: Signature made Tue Aug 21 14:20:20 2018 UTC
2018/08/21 19:17:06 debootstrap.log | gpgv: using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
2018/08/21 19:17:06 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>"
2018/08/21 19:17:06 debootstrap.log | gpgv: Signature made Tue Aug 21 14:20:20 2018 UTC
2018/08/21 19:17:06 debootstrap.log | gpgv: using RSA key 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC
2018/08/21 19:17:06 debootstrap.log | gpgv: Good signature from "Debian Archive Automatic Signing Key (9/stretch) <ftpmaster@debian.org>"
2018/08/21 19:17:06 debootstrap.log | mount: /proc: permission denied.
2018/08/21 19:17:06 Action `debootstrap` failed at stage Run, error: exit status 1
To overcome this /proc access issue I have decided to run the container in the
privileged mode.
Generally, I try to avoid doing that whenever not strictly required. Scoping the
actual access requirements and reducing the container access to the host system
might be another task to look at. For now, I’m sticking with the privileged
mode enabled without much deeper analysis.
One more issue
One more issue to solve was:
1
2
3
4
5
2018/08/21 14:17:53 debootstrap.log | Processing triggers for libc-bin (2.27-5) ...
2018/08/21 14:17:53 debootstrap.log | /debootstrap/debootstrap: 1363: /debootstrap/debootstrap: cannot open //var/lib/apt/lists/debootstrap.invalid_dists_buster_main|contrib|no
n-free_binary-arm64_Packages: No such file
2018/08/21 14:17:53 Action `debootstrap` failed at stage Run, error: exit status 2
Powering off.
It appears that there is a
debootstrap bug report
hanging in the Debian bug tracker since the Dec 2015. The issue
was resolved
in the debootstrap1.0.96. Unfortunately, the debootstrap version shipped
in my Debian Stretch container is 1.0.89. As a quick solution, I decided to
provide the patch manually:
After some struggle, I finally was able to build the image inside the docker
container. I consider it quite useful as it may enable more users (who do not
own the native Debian machine) to take advantage of the debos utility.
Hopefully, I can manage to push this idea upstream and some more people will
take advantage of my work.
Engineering Manager at 3mdeb with years of experience in engineering and management. Open-source software enthusiast and contributor. Interested in embedded systems in general, build systems, security.
.png){kind=small}
