Skip to main content
Flexible Top Header
Solved

V25.1.x docker builds failing due to issues within Debian apt sources

  • November 4, 2025
  • 3 replies
  • 21 views
M
  • martin
  • Active Resolver
  • 110 replies

Is anyone else out there experiencing failures when building custom containers using either v25.1.0 or v25.1.1 as their dockerfile FROM sources?

Example:

0.372 Get:1 http://deb.debian.org/debian bullseye InRelease [75.1 kB]                                                                                                                                                            
0.454 Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [27.2 kB]                                                                                                                                          
0.497 Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.0 kB]                                                                                                                                                    
0.543 Ign:4 http://deb.debian.org/debian bullseye-backports InRelease
0.581 Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8066 kB]
1.235 Get:6 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [422 kB]
1.300 Err:7 http://deb.debian.org/debian bullseye-backports Release
1.300   404  Not Found [IP: 146.75.30.132 80]
1.339 Get:8 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [18.8 kB]
1.933 Reading package lists...
2.231 E: The repository 'http://deb.debian.org/debian bullseye-backports Release' does not have a Release file.

I have a CARES ticket open for this, but maybe someone from the Gateway team will see this first and be able to resolve this quicker.

Yes, I know that v25.2.0 is the most recent, but I need to stick with python 3.9.2 for now (moving to 3.11 as I rewrite workflows using APIV2). I don’t have apt-get update failures when using 25.2.0, however.

Thanks,
Martin.

Best answer by martin

My Quick fix worked!
Created a new, temporary, sources.list file just without the bullseye-backports line, then copied that across during the docker build process, just before apt-get update is run, and container finally built.

However, gateway engineering team need to make the changes within their quay.io images to make this permanent.

    3 replies

    T
    Forum|alt.badge.img+2
    • tmaestas
    • Verified Resolver
    • 43 replies
    • November 4, 2025

    Debian Bullseye is EOL so the backports are no longer available in the main repo.  You could point to archive maybe instead?

    deb https://archive.debian.org/debian bullseye-backports main

     

    M
    • martin
    • Author
    • Active Resolver
    • 110 replies
    • November 4, 2025

    Debian Bullseye is EOL so the backports are no longer available in the main repo.  You could point to archive maybe instead?

    deb https://archive.debian.org/debian bullseye-backports main

     

    Would love to, but the debian repository config is set inside the bluecat provided quay.io docker image.
    Technically I could adjust this during dockerbuild time, copying new files across, but I want to keep the original image as intact as possible.
    Have to see what support comes back with on this.

    M
    • martin
    • Author
    • Active Resolver
    • 110 replies
    • Answer
    • November 4, 2025

    My Quick fix worked!
    Created a new, temporary, sources.list file just without the bullseye-backports line, then copied that across during the docker build process, just before apt-get update is run, and container finally built.

    However, gateway engineering team need to make the changes within their quay.io images to make this permanent.


    Terms & ConditionsCookie settingsAccessibility statement