TIBCOSoftware/js-docker image fails on start with "Failed to fetch...chromium"

Issue Description

A stale apt-get repository resulted in a restart error of an image. Months ago a customer used the TIBCOSoftware/js-docker scripts to build a docker image. They needed to restart the container, upon restart a failure occurred:

E: Failed to fetch http://deb.debian.org/debian/pool/main/s/systemd/systemd_241-7~deb10u5_amd64.deb 404 Not Found [iP: 1 99.232.130.132 80]

E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/c/chromium/chromium-common_87.0.4280.141-0 .1~deb10u1_amd64.deb 404 Not Found [iP: 151.101.250.132 80]

E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/c/chromium/chromium_87.0.4280.141-0.1~deb1 0u1_amd64.deb 404 Not Found [iP: 151.101.250.132 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Resolution

The ENTRYPOINT calls chromium-setup.sh which involves this command:

apt-get install -y --no-install-recommends chromium.

The failure occurs because the apt-get command is using an outdated package repository, in part because the image was built months ago and no statements indicated that apt-get should be refreshed.

To fix this problem you can add a command for "apt-get update" on line 30 of chromium-setup.sh prior to the "apt-get install -y --no-install-recommends chromium", which should refresh the package repository.  You'll need to rebuild the image.

Another option is to move the apt-get install directive for chromium out of the scripts called during the ENTRYPOINT and move them into the dockerfile.

Theoretically you can also just perform a new "git clone" if you only have short-term needs, but be mindful of Docker's build cache which will try to re-use unchanged instructions from prior dockerfiles for the sake of build performance. If you already have builds of the same dockerfile you can bypass build cache by adding "--nocache" to your build command, see https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#leverage-build-cache .

Ref. Case 01931613