Maximilian Gaß

I have a similar issue, which seems tied to pushing an image to the registry. All the build steps are cached and then Earthly takes a while before it begins...

If I remove `--push` from my call, it does not happen. If I add `--push`, it takes forever, *before* it starts pushing layers. The image that is eventually pushed to...

If I replace `--ci` with `--no-output --strict --use-inline-cache`, the problem goes away. So I assume the issue is with `--save-inline-cache`.

I would also like to have this ability and combine it with #1258, to avoid redeploys if nothing in an image actually changes.

RUN cd deploy && kustomize edit set image foo:latest $EXAMPLE1 SAVE IMAGE foo/deploy:latest I think this will not work because the digest cannot be known before the image is created....

> I believe you misunderstood my example. The SAVE IMAGE part you quoted is irrelevant for the RUN line above it, it merely demonstrates propagation of digests into stages descending...

@vladaionescu Since Dockerfile added this feature, this issue should be tagged as dockerfile-parity as well

I realized that my example above is not how recursive globbing usually works, because it would not keep the directory structure. I guess it would be better as: ``` COPY...

> I suppose that making the "totally arbitrary value" configurable is a great idea, and a low-hanging fruit. OTOH, it's also a bit of a band-aid... TBH I would prefer...

> With the current way of redirecting with a req=.. parameter, you can have to concurrent login flows in one browser, using cookies, this could become more complicated. I would...