You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to build the Docker image and the version pinned on the Dockerfile (2.38.1-5+deb12u1) could not install on my system. I removed the version pinned and then I could build the image. Is the version pinning mandatory?
I am on Ubuntu 24.04.
Before:
DVUEFI$ docker build --tag dvuefi-build edk2-build-toolchain
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Sending build context to Docker daemon 6.656kB
Step 1/5 : FROM debian:latest
latest: Pulling from library/debian
fdf894e782a2: Pull complete
Digest: sha256:17122fe3d66916e55c0cbd5bbf54bb3f87b3582f4d86a755a0fd3498d360f91b
Status: Downloaded newer image for debian:latest
---> ff869c3288a4
Step 2/5 : RUN set -eu && apt update && apt --no-install-recommends -y install build-essential=12.9 uuid-dev=2.38.1-5+deb12u1 acpica-tools=20200925-8 git nasm=2.16.01-1 python-is-python3
---> Running in ce8aa3188e94
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8789 kB]
Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [8856 B]
Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [216 kB]
Fetched 9268 kB in 1s (8587 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
uuid-dev : Depends: libuuid1 (= 2.38.1-5+deb12u1) but 2.38.1-5+deb12u2 is to be installed
E: Unable to correct problems, you have held broken packages.
The command '/bin/sh -c set -eu && apt update && apt --no-install-recommends -y install build-essential=12.9 uuid-dev=2.38.1-5+deb12u1 acpica-tools=20200925-8 git nasm=2.16.01-1 python-is-python3' returned a non-zero code: 100
After:
DVUEFI$ docker build --tag dvuefi-build edk2-build-toolchain
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Sending build context to Docker daemon 6.656kB
Step 1/5 : FROM debian:latest
---> ff869c3288a4
Step 2/5 : RUN set -eu && apt update && apt --no-install-recommends -y install build-essential=12.9 uuid-dev acpica-tools=20200925-8 git nasm=2.16.01-1 python-is-python3
---> Running in 0d0016c2c998
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8789 kB]
Get:5 http://deb.debian.org/debian bookworm-updates/main amd64 Packages [8856 B]
Get:6 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [216 kB]
Fetched 9268 kB in 1s (8531 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
binutils binutils-common binutils-x86-64-linux-gnu bzip2 cpp cpp-12 dpkg-dev
[...]
Setting up build-essential (12.9) ...
Processing triggers for libc-bin (2.36-9+deb12u9) ...
---> Removed intermediate container 0d0016c2c998
---> 1319c76937d6
Step 3/5 : WORKDIR /home
---> Running in 31f6357db0e2
---> Removed intermediate container 31f6357db0e2
---> ca21a2219bf1
Step 4/5 : VOLUME vuln-edk2
---> Running in 9aafb1f6f192
---> Removed intermediate container 9aafb1f6f192
---> 0cfdc59ae237
Step 5/5 : CMD ["bash"]
---> Running in f09a88df8846
---> Removed intermediate container f09a88df8846
---> bc0e9c0600e2
Successfully built bc0e9c0600e2
Successfully tagged dvuefi-build:latest
The text was updated successfully, but these errors were encountered:
Yeah, looks like some of the pinned packages are no longer available: thanks for bringing this up!
Everything should work fine without pinning, but I would like to work toward having a long term solution for everyone to produce repeatable builds and run the firmware in a similar environment (e.g. same version of qemu). We can leave the issue open and I'll update it when there's a better solution for pinning.
Hi!
I was trying to build the Docker image and the version pinned on the Dockerfile (
2.38.1-5+deb12u1
) could not install on my system. I removed the version pinned and then I could build the image. Is the version pinning mandatory?I am on Ubuntu 24.04.
Before:
After:
The text was updated successfully, but these errors were encountered: