Old docker image after returning to challenge

Platform
1

Hey,

recently I decided to come back to the Redis challenge. I have started the challenge a while back, meaning the repository is a bit older.

When I now want to test code and get the following error:

[build] Step 8 complete.                                                                                                                                                                                                                                                                   
[build] > Ign:1 http://deb.debian.org/debian buster InRelease
[build] > Ign:2 http://deb.debian.org/debian-security buster/updates InRelease                                                                                                                                                                                                             
[build] > Ign:3 http://deb.debian.org/debian buster-updates InRelease
[build] > Err:4 http://deb.debian.org/debian buster Release
[build] >   404  Not Found [IP: 146.75.30.132 80]                   
[build] > Err:5 http://deb.debian.org/debian-security buster/updates Release
[build] >   404  Not Found [IP: 146.75.30.132 80]
[build] > Err:6 http://deb.debian.org/debian buster-updates Release
[build] >   404  Not Found [IP: 146.75.30.132 80]                   
[build] > Reading package lists...
[build] > E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
[build] > E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
[build] > E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
[build] Error: process "/bin/sh -c apt-get update && apt-get install -y git curl" did not complete successfully: exit code: 100.                                                                                                                                                           
[build] > Err:4 http://deb.debian.org/debian buster Release                                                                                                                                                                                                                                
[build] >   404  Not Found [IP: 146.75.30.132 80]
[build] > Err:5 http://deb.debian.org/debian-security buster/updates Release
[build] >   404  Not Found [IP: 146.75.30.132 80]
[build] > Err:6 http://deb.debian.org/debian buster-updates Release
[build] >   404  Not Found [IP: 146.75.30.132 80]
[build] > Reading package lists...
[build] > E: The repository 'http://deb.debian.org/debian buster Release' does not have a Release file.
[build] > E: The repository 'http://deb.debian.org/debian-security buster/updates Release' does not have a Release file.
[build] > E: The repository 'http://deb.debian.org/debian buster-updates Release' does not have a Release file.
[build] Build failed. Check the logs above for the reason.
[build] If you think this is a CodeCrafters error, please contact us at hello@codecrafters.io.

How can I update the docker image, as buster is EOL and the mirror does not exist anymore.

Greetings

2

Hey @Liikt, your repo was using an older Rust buildpack (v1.70). I’ve upgraded it to v1.88 and pushed a few commits to your repo. You can run git pull to sync the latest changes.

Let me know if you hit any other issues!

3

Nice it works now. Thank you very much :slight_smile:

1 Like
4

I am encountering an exact same problem with my old Rust repos. Is there a way to fix this problem without support intervention, i.e. update it to v1.88 myself ? I tried doing it but got:

remote: Detected changes to language_pack (old: rust-1.77, new: rust-1.88).
remote: This isn’t supported. If you’re trying to upgrade to a new language version, please try creating a new repository.
remote: If you think this is a CodeCrafters bug, please contact us at hello@codecrafters.io.

A workaround for me was to keep the source code, start again from the beginning from the first step and then paste the source code. But maybe there is a simpler way?

5

A workaround for me was to keep the source code, start again from the beginning from the first step and then paste the source code. But maybe there is a simpler way?

Hey @amoilanen, unfortunately that’s currently the only way to “upgrade” a buildpack yourself.

Let me know if you’d like me to upgrade any of your old repos for you.

6

Thanks, I will probably upgrade the repos myself using the outlined workaround (it seems to work). I will reach out if there are any technical difficulties

1 Like