Debian stretch packages not found (affecting README / Docker demo)

[rdck]

The README suggests using the container based on Debian stretch, but it looks like the stretch packages aren't available where they're expected to be. I assume they moved when stretch reached end of LTS. Can we build from a more recent Debian release?

> podman build -t liballocs_built liballocs/buildtest/debian-stretch
WARN[0000] missing "user" build argument. Try adding "--build-arg user=<VALUE>" to the command line
STEP 1/13: FROM debian:stretch
STEP 2/13: ARG user
--> Using cache 788a879a82eb8b858ef50ea0d4b94fcb8213156652e8c90a5afbfd030be132f9
--> 788a879a82eb
STEP 3/13: RUN apt-get update && apt-get install -y sudo
Ign:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://security.debian.org/debian-security stretch/updates Release
Ign:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Ign:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Ign:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Ign:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Ign:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Err:3 http://security.debian.org/debian-security stretch/updates/main amd64 Packages
  404  Not Found [IP: 151.101.194.132 80]
Ign:4 http://security.debian.org/debian-security stretch/updates/main all Packages
Ign:5 http://deb.debian.org/debian stretch InRelease
Ign:6 http://deb.debian.org/debian stretch-updates InRelease
Ign:7 http://deb.debian.org/debian stretch Release
Ign:8 http://deb.debian.org/debian stretch-updates Release
Ign:9 http://deb.debian.org/debian stretch/main amd64 Packages
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Ign:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Ign:9 http://deb.debian.org/debian stretch/main amd64 Packages
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Ign:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Ign:9 http://deb.debian.org/debian stretch/main amd64 Packages
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Ign:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Ign:9 http://deb.debian.org/debian stretch/main amd64 Packages
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Ign:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Ign:9 http://deb.debian.org/debian stretch/main amd64 Packages
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Ign:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Err:9 http://deb.debian.org/debian stretch/main amd64 Packages
  404  Not Found [IP: 146.75.38.132 80]
Ign:10 http://deb.debian.org/debian stretch/main all Packages
Err:11 http://deb.debian.org/debian stretch-updates/main amd64 Packages
  404  Not Found [IP: 146.75.38.132 80]
Ign:12 http://deb.debian.org/debian stretch-updates/main all Packages
Reading package lists...
W: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file.
W: The repository 'http://deb.debian.org/debian stretch Release' does not have a Release file.
W: The repository 'http://deb.debian.org/debian stretch-updates Release' does not have a Release file.
E: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.194.132 80]
E: Failed to fetch http://deb.debian.org/debian/dists/stretch/main/binary-amd64/Packages  404  Not Found [IP: 146.75.38.132 80]
E: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/main/binary-amd64/Packages  404  Not Found [IP: 146.75.38.132 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error: building at STEP "RUN apt-get update && apt-get install -y sudo": while running runtime: exit status 100

[rdck]

I see there is discussion of this already in #122.

[stephenrkell]

Reopening this, because it's a valid report w.r.t. the README and is fixable separately from whatever issues affect trixie.

I haven't kept up with whether anything is failing with Debian trixie just now -- that thread is a bit old. But we do have CI running on Ubuntu 24.04 which is significantly newer than Debian stretch. So one way or another, it is possible to update the container demo. I'll have a go at this shortly.

[stephenrkell]

There's a rough cut at a solution in 088f6e3 -- the idea being to make a Dockerfile that closely mirrors the current CircleCI config, and make the README reference that.

[stephenrkell]

The one thing I would like to do that this "rough cut" does not is a Docker recipe that does not re-clone from GitHub but instead somehow slurps from the host system, at the user's option, either (1) the committed git history in the containing git repo at the time of execution, or (2) the committed git history and staged modifications in the containing git repo at the time of execution.

The latter would enable a workflow where I don't have to commit and push to CI to find out that I've broken things in the CI environment even though they "work for me"... I could test them immediately before committing.

If anyone with better Docker-fu than me can suggest how to do this, I'm all ears. I guess I can mount (when running Docker), then clone from that mount (inside the container), then patch (also inside the container, if I want the staged changes).

Of course I probably also want a version that does just pull down a pristine clone. Though maybe that is best saved for actual-CI, and the buildtest rules can be specialised to this local thing.