Bintray repository fix - E: Failed to fetch https://dl.bintray.com/sbt/debian/InRelease

If your Compute Environment's dockerfile instructions contains "apt-get update" or "apt update" and the base image is based on the DAD, you may encounter an error while trying to revise then build that Environment.  See below for details.

As of the 4th of July, 2021, the JFrog Bintray service has been sunset and is no longer operational.

Please see the following links for additional information:

https://status.bintray.com/

https://jfrog.com/center-sunset/

The Bintray service is referenced by Ubuntu's apt-get package manager in our Domino Analytics Distribution environments (DAD).

This can cause build errors in ALL Domino images that are based upon our default Domino Analytics Distribution environment (DAD).  The trigger which causes the error upon build is the presence of Dockerfile instructions involving commands "apt-get update" or "apt update". 

Please consider the following two options to avoid the environment build error failed to fetch e: https://dl.bintray.com/sbt/debian/InRelease.

Option 1) Add the below code to the top of your dockerfile.

If you would prefer to maintain the same DAD version as your base image, add this code to the top of your dockerfile.

NOTE: Once your base image is corrected with this code, remove the code or remove the apt remove commands: && apt -y remove sbt && apt -y purge sbt

# if you also have the nvidia repo fix, put this AFTER that
RUN rm -f /etc/apt/sources.list.d/sbt.list && \
 sed 's/deb http:\/\/apt.postgresql.org\/pub\/repos\/apt\/ precise-pgdg main//' /etc/apt/sources.list.d/pgdg.list -i && \
 sed -i 's/precise/bionic/g' /etc/apt/sources.list.d/pgdg.list && \
 # Correct GPG key expiration for cloud.r-project.org -- https://community.dominodatalab.com/post/editdiscussion/484
    gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys E298A3A825C0D65DFD57CBB651716619E084DAB9 && \
    gpg -a --export E298A3A825C0D65DFD57CBB651716619E084DAB9 | sudo apt-key add - && \
    apt update -qqq && apt -y remove sbt && apt -y purge sbt
RUN curl -L https://github.com/sbt/sbt/releases/download/v1.4.7/sbt-1.4.7.tgz --output /tmp/sbt.tgz && \
 cd /usr/share && \
 tar xfz /tmp/sbt.tgz && \
 ln -sf /usr/share/sbt/bin/sbt /usr/bin/sbt && \
 rm -f /tmp/sbt.tgz

Caveat - port 80 or hkp not working

(this can lead to neverending timeout)

# if you also have the nvidia repo fix, put this AFTER that
RUN rm -f /etc/apt/sources.list.d/sbt.list && \
 sed 's/deb http:\/\/apt.postgresql.org\/pub\/repos\/apt\/ precise-pgdg main//' /etc/apt/sources.list.d/pgdg.list -i && \
 sed -i 's/precise/bionic/g' /etc/apt/sources.list.d/pgdg.list && \
 # Correct GPG key expiration for cloud.r-project.org -- https://community.dominodatalab.com/post/editdiscussion/484
curl -sSL \
'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xE298A3A825C0D65DFD57CBB651716619E084DAB9' \
  | sudo apt-key add -
RUN apt update -qqq && apt -y remove sbt && apt -y purge sbt || echo IgnoreError
RUN curl -L https://github.com/sbt/sbt/releases/download/v1.4.7/sbt-1.4.7.tgz --output /tmp/sbt.tgz && \
 cd /usr/share && \
 tar xfz /tmp/sbt.tgz && \
 ln -sf /usr/share/sbt/bin/sbt /usr/bin/sbt && \
 rm -f /tmp/sbt.tgz

Option 2) Update your DAD base image

For a more permanent fix, you can rebuild your image using our latest version of the DAD that no longer attempts to load the bintray repo. 

1. First, find the latest version of our DAD in quay.io (or docker.io for deprecated versions).
2. Add it to your organization's container registry (Quay, Dockhub, etc.) Use the Fetch Tag, to view the Pull Tag for the appropriate format.
3. Now you can use it as your base image when building the environment. Example below:
   

If you're new to environment management, consider reviewing our docs site:  https://docs. dominodatalab.com/en/4.5/ reference/environments/Video_ introduction_to_Domino_ Environmen...

NOTE: Starting with our next minor release of Domino (v4.5.1), new installations will have the fixed DAD pre-installed for use. However, the time of that release is TBD.