Cannot apt-get update with deno base image

[justinmchase]

FROM docker.repo1.uhc.com/denoland/deno:1.13.0

RUN apt-get update && \
    apt-get install -y \
    apt-transport-https \
    ca-certificates \
    curl

Results in an error:

The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file.

Details:

 => ERROR [ 2/10] RUN apt-get update &&     apt-get install -y     apt-transport-https     ca-certificates     curl                                                                                                                                                                                 5.2s
------                                                                                                                                                                                                                                                                                                                        
 > [ 2/10] RUN apt-get update &&     apt-get install -y     apt-transport-https     ca-certificates     curl:                                                                                                                                                                                            
#5 0.333                                                                                                                                                                                                                                                                                                                      
#5 0.333 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.                                                                                                                                                                                                                                      
#5 0.333                                                                                                                                                                                                                                                                                                                      
#5 0.581 Ign:1 http://security.debian.org/debian-security stable/updates InRelease                                                                                                                                                                                                                                            
#5 0.585 Get:2 http://deb.debian.org/debian stable InRelease [113 kB]
#5 0.630 Err:3 http://security.debian.org/debian-security stable/updates Release
#5 0.630   404  Not Found [IP: 151.101.130.132 80]
#5 0.981 Get:4 http://deb.debian.org/debian stable-updates InRelease [36.8 kB]
#5 1.144 Get:5 http://deb.debian.org/debian stable/main amd64 Packages [8178 kB]
#5 4.298 Reading package lists...
#5 5.172 E: The repository 'http://security.debian.org/debian-security stable/updates Release' does not have a Release file.
------
executor failed running [/bin/sh -c apt-get update &&     apt-get install -y     apt-transport-https     ca-certificates     curl]: exit code: 100

This just started happening this morning for me, multiple machines are encountering it. Last Friday it was working fine... I've seen some answers on SO for this issue, such as:

https://unix.stackexchange.com/a/371907/446793

Which are pretty old so I'm not sure what's going on. Perhaps the version of base images Deno is relying on needs to be updated? I'm not really sure.

[justinmchase]

This is failing, for me all by itself:

FROM debian:stable-slim
RUN apt-get update

So either I have some bizarre caching issue or its lower down from Deno.

[justinmchase]

Switching to denoland/deno:ubuntu-1.13.0 fixes it. So it seems like there is an issue with the downstream debian:stable-slim image.

[justinmchase]

I just happened to notice this "popular issue" reported by github and it seems related:

debuerreotype/docker-debian-artifacts#122

[hayd]

fixed now?

[wperron]

Closing as this is an upstream issue.

[justinmchase]

@hayd I believe its fixed now. I just happened to catch it in the middle of a slow rolling update which leaves various upstream users in a bad state until its done.