Docker build image error

[denxtrix]

Hi,
I am new to Docker and am trying unsuccessfully to create a Debian (Trixie) image for my Rock_5c SBC using the command:
docker build -t sd-images https://github.com/johang/sd-card-images.git

I get the following error:

:~$ sudo docker build -t sd-images https://github.com/johang/sd-card-images.git
[+] Building 11.0s (4/7) docker:default
=> CACHED [internal] load git source https://github.com/johang/sd-card-images.git 1.1s
=> [internal] load metadata for public.ecr.aws/ubuntu/ubuntu:24.04 1.1s
=> CACHED [1/5] FROM public.ecr.aws/ubuntu/ubuntu:24.04@sha256:6b4c0f97bc73e76ac20ef992258e9b8c831b7755d2047d83109da8eb279881fe 0.0s
=> => resolve public.ecr.aws/ubuntu/ubuntu:24.04@sha256:6b4c0f97bc73e76ac20ef992258e9b8c831b7755d2047d83109da8eb279881fe 0.0s
=> ERROR [2/5] RUN apt-get update && apt-get --assume-yes ...

Thanks

[denxtrix]

I looked in the Dockerfile :

" FROM public.ecr.aws/ubuntu/ubuntu:24.04
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && \ "

I think the wrong registry is being used to create a Debian Trixie image.
Should I change the registry?

[denxtrix]

Would it be possible to see the Dockerfile used to create the Debian testing (“forky”) image distributed on https://sd-card-images.johang.se/boards/rock_5c.html?

[johang]

It's the same image.

[denxtrix]

I don't understand the answer. What is the same image?

[itsiiie]

The Dockerfile is using Ubuntu intentionally as a build environment, not as the final OS.

The Debian (testing/trixie) system is created later inside the container using debootstrap.
So Ubuntu is just the toolbox used to build the SD card image, and the final image is still Debian.

The apt-get update failure is happening in the minimal Ubuntu 24.04 base image and is not related
to Debian or the target image itself.

When I said “it’s the same image”, I meant the same build pipeline is used for the published SD
card images and for this repo, not that the Docker base image is Debian.

[denxtrix]

Thank you for this explanation, which helps me better understand the process of creating an image with Dockerfile.
However, I don't understand what is causing the error with apt-get update in the Ubuntu environment when building the Debian trixie image for my rock_5c. Perhaps it is related to my Docker configuration or the system and hardware I am using. See my configuration below:
rock-5c
OS: Debian 12 bookworm
Kernel: aarch64 Linux 6.1.84-6-rk2410
Uptime: 7m
Packages: 1207
Shell: bash 5.2.15
Disk: 6.6G / 114G (7%)
CPU: ARM - - - - - - - - - - - - - - - @ 8x 1.8GHz
RAM: 382MiB / 7939MiB

[itsiiie]

Your host OS and hardware (Debian 12 on Rock 5C / ARM64) are not the cause of the issue.

The failure happens inside the Docker build, before anything related to the target
Debian trixie image is created. At that stage, the container is running Ubuntu 24.04
from public.ecr.aws/ubuntu, which is a very minimal base image.

On ARM/aarch64, apt-get update in that image can fail due to:

• temporary mirror/release metadata changes
• missing release-info acceptance
• minimal apt configuration in the base image

This is independent of:

• Rock 5C hardware
• Debian 12 host OS
• Docker configuration on the host

A common workaround is to make the apt step more tolerant, for example:

• apt-get update --allow-releaseinfo-change
• or switching to a different Ubuntu mirror
• or documenting this as a known limitation of the minimal Ubuntu base image

Once debootstrap runs, the Debian trixie filesystem is built correctly and does not
depend on the Ubuntu environment anymore.

[johang]

Thanks, @itsiiie. The Docker image builds are OK in Actions.

[denxtrix]

What am I supposed to do to build an image?

• Clone https://github.com/johang/sd-card-images.git on my machine
• Modify Dockerfile
• ...

[itsiiie]

You do not need to modify the Dockerfile to build an image.

The intended workflow is:

1. Clone the repository:

   git clone https://github.com/johang/sd-card-images.git
   cd sd-card-images

2. Build the Docker build environment:

   docker build -t sd-images .

   This only creates a container with all required build tools
   (qemu, cross-compilers, debootstrap, etc).
   It does NOT create the Debian image yet.

3. Run the build script for your board:

   ./build.sh rock-5c trixie

   During this step:

   • debootstrap downloads Debian trixie
   • the Debian root filesystem is created
   • bootloader/kernel/partitions are assembled
   • the final SD card image is generated

So you should:
✔ clone the repo
✔ build the Docker image
✔ run the provided build script

You should NOT need to modify the Dockerfile unless you are changing
the build environment itself.

[denxtrix]

I understand the different procedures for building an image, whether with
: ~$ sudo docker build -t sd-images https://github.com/johang/sd-card-images.git
or with
: ~/sd-card-images$ sudo docker build -t sd-images .

But neither works because the error persists with apt-update. See the exit code below :

[+] Building 9.8s (6/9)
docker:default
=> [internal] load build definition from Dockerfile => => transferring dockerfile: 2.06kB
=> [internal] load metadata for public.ecr.aws/ubuntu/ubuntu:24.04
=> [internal] load .dockerignore
=> => transferring context: 58B
=> CACHED [1/5] FROM public.ecr.aws/ubuntu/ubuntu:24.04@sha256:2840d5f4a6a1a8eb11e0d493bf0bbc030442d48e902e99bbc7127b76f9775b1e
=> => resolve public.ecr.aws/ubuntu/ubuntu:24.04@sha256:2840d5f4a6a1a8eb11e0d493bf0bbc030442d48e902e99bbc7127b76f9775b1e
=> [internal] load build context
=> => transferring context: 4.58kB
=> ERROR [2/5] RUN apt-get update && apt-get --assume-yes --no-install-recommends install debootstrap debian-archive-keyring ca-certificates qe 8.5s

[2/5] RUN apt-get update && apt-get --assume-yes --no-install-recommends install debootstrap debian-archive-keyring ca-certificates qemu-user qemu-user-static qemu-system-arm qemu-system-x86 device-tree-compiler gcc gcc-arm-none-eabi make git bc bzip2 pigz bison flex python3-dev python3-pkg-resources python3-pyelftools python3-setuptools swig parted e2fsprogs dosfstools mtools pwgen libssl-dev libgnutls28-dev uuid-dev parallel ssh sshpass unzip && ([ "$(uname -m)" = "aarch64" ] && apt-get --assume-yes install gcc-arm-linux-gnueabihf gcc-i686-linux-gnu gcc-x86-64-linux-gnu || :) && ([ "$(uname -m)" = "x86_64" ] && apt-get --assume-yes install gcc-arm-linux-gnueabihf gcc-aarch64-linux-gnu gcc-i686-linux-gnu || :) && apt-get clean && rm -rf /var/lib/apt/lists/* && rm -f /var/log/*.log:
0.481 Ign:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
0.595 Ign:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease
0.712 Ign:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
0.831 Ign:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
1.607 Ign:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
1.728 Ign:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease
1.848 Ign:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
1.966 Ign:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
3.733 Ign:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
3.854 Ign:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease
3.973 Ign:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
4.093 Ign:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
7.855 Err:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
7.855 Temporary failure resolving 'ports.ubuntu.com'
7.977 Err:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease
7.977 Temporary failure resolving 'ports.ubuntu.com'
8.097 Err:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
8.097 Temporary failure resolving 'ports.ubuntu.com'
8.218 Err:4 http://ports.ubuntu.com/ubuntu-ports noble-security InRelease
8.218 Temporary failure resolving 'ports.ubuntu.com'
8.238 Reading package lists...
8.311 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble/InRelease Temporary failure resolving 'ports.ubuntu.com'
8.311 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble-updates/InRelease Temporary failure resolving 'ports.ubuntu.com'
8.311 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble-backports/InRelease Temporary failure resolving 'ports.ubuntu.com'
8.311 W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble-security/InRelease Temporary failure resolving 'ports.ubuntu.com'
8.311 W: Some index files failed to download. They have been ignored, or old ones used instead.
8.361 Reading package lists...
8.392 Building dependency tree...
8.394 Reading state information...
8.398 Package ca-certificates is not available, but is referred to by another package.
8.398 This may mean that the package is missing, has been obsoleted, or
8.398 is only available from another source
...