Skip to content
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.

Commit

Permalink
Bump Chrome patch version, bump FF to 88.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@baflQA
baflQA committed Apr 21, 2021
1 parent bd40b75 commit 63d31e3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Dockerfile
View file
Original file line number Diff line number Diff line change
Expand Up @@ -429,7 +429,7 @@ ENV FF_LANG="en-US" \
FF_PLATFORM="linux-x86_64" \
FF_INNER_PATH="firefox/releases"

ARG FF_VER="87.0"
ARG FF_VER="88.0"

ENV FF_COMP="firefox-${FF_VER}.tar.bz2"
ENV FF_URL="${FF_BASE_URL}/${FF_INNER_PATH}/${FF_VER}/${FF_PLATFORM}/${FF_LANG}/${FF_COMP}"
Expand Down Expand Up @@ -466,7 +466,7 @@ COPY bin/fail /usr/bin/
#===============
# TODO: Use Google fingerprint to verify downloads
# https://www.google.de/linuxrepositories/
ARG EXPECTED_CHROME_VERSION="90.0.4430.72"
ARG EXPECTED_CHROME_VERSION="90.0.4430.85"
ENV CHROME_URL="https://dl.google.com/linux/direct" \
CHROME_BASE_DEB_PATH="/home/seluser/chrome-deb/google-chrome" \
GREP_ONLY_NUMS_VER="[0-9.]{2,20}"
Expand Down

3 comments on commit 63d31e3

@baflQA
Copy link
Collaborator Author

@baflQA baflQA commented on 63d31e3 Apr 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elgalu can You please have a look at CI/CD? It seems not to be running recently on merge.

@elgalu
Copy link
Owner

@elgalu elgalu commented on 63d31e3 Apr 24, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Let me see what can I do

@elgalu
Copy link
Owner

@elgalu elgalu commented on 63d31e3 Apr 24, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doing docker login before any docker operation seems to fix the problem!

Thanks for caring<3

Please sign in to comment.