Repository navigation
Fix or remove jpribyl/action-docker-layer-caching action in pipeline #1919
Description
Description
I've never seen the jpribyl/action-docker-layer-caching action actually run without throwing a warning that it failed to retrieve the cache.
It seems broken, whenever it runs it takes up to 2m30s.
Warning: Failed to restore: getCacheEntry failed: Request timeout: /.../_apis/artifactcache/cache?keys=docker-layer-caching-CI%2FCD-%7Bhash%7D%2Cdocker-layer-caching-CI%2FCD-&version=...
Root cache could not be found. aborting.
Example runs:
- https://github.com/openremote/openremote/actions/runs/15411435674/job/43364099838
- https://github.com/openremote/openremote/actions/runs/15421204844/job/43396498331
- https://github.com/openremote/openremote/actions/runs/15444335892/job/43469766836
- https://github.com/openremote/openremote/actions/runs/15440913083/job/43458271167
- https://github.com/openremote/openremote/actions/runs/15426889243/job/43415964938
We should investigate whether this action is needed if the manager docker build is only 30 seconds. I don't see any caches related to this job anyways, see https://github.com/openremote/openremote/actions/caches.
Metadata
Metadata
Assignees
Labels
No labels
Activity
Ekhorn commentedon Jun 19, 2025
Suddenly the timeout is significantly reduced in this pipeline run compared to the previously mentioned ones: https://github.com/openremote/openremote/actions/runs/15759305561/job/44421884511
denniskuijs commentedon Sep 5, 2025
It looks like the action isn't working anymore.
In the last run here the cache service responded with error code
400and returns the following error message:Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>wborn commentedon Nov 27, 2025
We might want to look into replacing it with the docker/build-push-action which is better maintained, see https://docs.docker.com/build/ci/github-actions/cache/
Ekhorn commentedon Nov 27, 2025
Ye, I tried to do so here c9ac257, but I likely need to enable expiremental features in the docker daemon-config. We could use https://github.com/docker/setup-docker-action to do so.
Ekhorn commentedon Apr 14, 2026
The following page explains what we can do: https://docs.docker.com/build/cache/backends/gha/
But we likely need to use a third-party action crazy-max/ghaction-github-runtime in addition (which they reference in their docs), because we use
docker buildx.wborn commentedon Apr 14, 2026
I used the docker/build-push-action in openremote/proxy#26. It seems to do multi arch as well as you can specify multiple
platforms. As it is by Docker it is more commonly used and there will be less of a risk for supply chain attacks and it becoming unmaintained.