Replies: 2 comments 2 replies
-
It's one of those old Docker Inc. tooling features with little value, nowadays. Using a fixed SemVer |
Beta Was this translation helpful? Give feedback.
1 reply
-
Use full locked image identifier: # syntax=docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021
FROM docker.io/library/golang:1.21-alpine3.18@sha256:9390a996e9f957842f07dff1e9661776702575dd888084e72d86eaa382ad56e3 as builder
... this way the resolver has enough info to do an image cache check. If then there are still network calls (on a cache hit) then there's a bug. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using the gitlab shell executor to run
and my dockerfile looks like
The execution result is like this
Can anyone help me why "resolve image config for docker.io/docker/dockerfile:1" and "load metadata for docker.io/library/alpine:3.18" take so long? I know China's international network connections are very slow, but these images should be cached locally and don't need to request the network every time, right? What can I do to speed things up?
Beta Was this translation helpful? Give feedback.
All reactions