zrhoffman opened a new issue #5499: URL: https://github.com/apache/trafficcontrol/issues/5499
<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at [email protected] and follow the guidelines at https://www.apache.org/security/ regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the Traffic Control slack (https://s.apache.org/atc-slack) or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR. --> ## I'm submitting a ... <!-- delete all those that don't apply --> <!--- security vulnerability (STOP!! - see above)--> - bug report ## Traffic Control components affected ... <!-- delete all those that don't apply --> - CI tests ## <div id="current-behavior">Current behavior:</div> <!-- Describe how the bug manifests --> Some of our actions are failing at the point where it builds the Dockerfile due to the Docker Hub saying *authentication required*. ```dockerfile Step 1/6 : FROM alpine:3.12 3.12: Pulling from library/alpine 801bfaa63ef2: Pulling fs layer 801bfaa63ef2: Downloading unauthorized: authentication required ``` This implies that the runners are hitting the Docker Hub's [pull rate limit](https://www.docker.com/blog/checking-your-current-docker-pull-rate-limits-and-status/), which restricts each IP address to 100 unauthenticated pulls per 6 hours. To get around this limitation, we can cache common base images like Alpine in GitHub Actions so that building our own Dockerfiles does not require pulls that count towards the Docker Hub's limit. ## Expected behavior: <!-- Describe what the behavior would be without the bug --> Our Dockerfiles should build without requiring Docker Hub authentication. ## Minimal reproduction of the problem with instructions: <!-- If the current behavior is a bug, please provide the *STEPS TO REPRODUCE* and include the applicable TC version. --> Since each GHA run where this has happened has been re-run, I am unable to find any run to link to that shows this problem. See the [*Current behavior*](#user-content-current-behavior) section for what the Docker build log shows when it does occur. <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at https://apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
