Currently, when trying to build the Docker image, errors related to Debian stretch packages being removed from the main repos (1) are generated. Adding the archive subdomain in this Dockerfile fixes the bug.
The errors can be seen below:
Err:10 http://deb.debian.org/debian stretch/main amd64 Packages
404 Not Found
Ign:11 http://deb.debian.org/debian stretch-updates/main all Packages
Err:12 http://deb.debian.org/debian stretch-updates/main amd64 Packages
404 Not Found
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
E: Failed to fetch http://deb.debian.org/debian/dists/stretch/main/binary-amd64/Packages 404 Not Found
E: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
The command '/bin/sh -c apt-get -y update' returned a non-zero code: 100
Additionally, the RUN commands are optimized to follow Docker best practices (2).
Currently, when trying to build the Docker image, errors related to Debian stretch packages being removed from the main repos (1) are generated. Adding the archive subdomain in this Dockerfile fixes the bug.
The errors can be seen below:
Additionally, the RUN commands are optimized to follow Docker best practices (2).