[PR #768] [MERGED] Cache dockerhub images from linux for macOS #1597

New issue

Closed

opened 2026-03-01 21:51:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:51:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/768
Author: @ChristopherHX
Created: 8/8/2021
Status: ✅ Merged
Merged: 8/31/2021
Merged by: @cplee

Base: master ← Head: patch-2

📝 Commits (5)

b5ade3d Cache dockerhub images from linux for macOS
02df67f parallelize / refactor docker cache
420f358 Merge branch 'master' into patch-2
c4cc951 Merge branch 'master' into patch-2
2894487 Merge branch 'master' into patch-2

📊 Changes

1 file changed (+55 additions, -2 deletions)

View changed files

📝 .github/workflows/checks.yml (+55 -2)

📄 Description

An attempt to avoid hitting the dockerhub Pull Rate Limit.

There is a small overhead due to caching (ca. +2 min, next run within 7 days only some seconds), but it might avoid rerunning the macOS job due to this error.
Restoreing the cache doesn't take much extra job execution time, because the test step is pulling less images from dockerhub.

This PR failed due to this limit #776.
It seems to be triggered by multiple PR's are opened within some days.

Needs more testing, if this solves the dockerhub limit problems or only delays the problem to happen less frequently.

Add new dockerhub images to CACHED_DOCKER_IMAGES and increment the cache key (CACHED_DOCKER_IMAGES_KEY)

What do you think?

I need ACT_OWNER: ${{ github.repository_owner }} and ACT_REPOSITORY: ${{ github.repository }} to have all tests green within my fork

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/768 **Author:** [@ChristopherHX](https://github.com/ChristopherHX) **Created:** 8/8/2021 **Status:** ✅ Merged **Merged:** 8/31/2021 **Merged by:** [@cplee](https://github.com/cplee) **Base:** `master` ← **Head:** `patch-2` --- ### 📝 Commits (5) - [`b5ade3d`](https://github.com/nektos/act/commit/b5ade3d9a5d4f58342d55448033700873d48c901) Cache dockerhub images from linux for macOS - [`02df67f`](https://github.com/nektos/act/commit/02df67fe994ef46ad49384699e8fb3faa26f51be) parallelize / refactor docker cache - [`420f358`](https://github.com/nektos/act/commit/420f358ab6e47cf349d4b4e5595a55985cb66e1d) Merge branch 'master' into patch-2 - [`c4cc951`](https://github.com/nektos/act/commit/c4cc951ae85f3aa92a66edf128dc7c56d71d0d0f) Merge branch 'master' into patch-2 - [`2894487`](https://github.com/nektos/act/commit/289448748751fa6d6ae1ba732182dec17e3535e6) Merge branch 'master' into patch-2 ### 📊 Changes **1 file changed** (+55 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/checks.yml` (+55 -2) </details> ### 📄 Description An attempt to avoid hitting the dockerhub Pull Rate Limit. There is a small overhead due to caching (ca. +2 min, next run within 7 days only some seconds), but it might avoid rerunning the macOS job due to this error. Restoreing the cache doesn't take much extra job execution time, because the test step is pulling less images from dockerhub. This PR failed due to this limit #776. It seems to be triggered by multiple PR's are opened within some days. _Needs more testing, if this solves the dockerhub limit problems or only delays the problem to happen less frequently._ Add new dockerhub images to `CACHED_DOCKER_IMAGES` and increment the cache key (`CACHED_DOCKER_IMAGES_KEY`) What do you think? _I need ACT_OWNER: ${{ github.repository_owner }} and ACT_REPOSITORY: ${{ github.repository }} to have all tests green within my fork_ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-01 21:51:51 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-03-01 21:53:41 +03:00

[PR #1597] [MERGED] Update max container name length #2022

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1597

No description provided.

Rows
Columns