-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to get layer #79
Comments
Did you ever figure out what was going on? I'm getting the same issue -- the spring-boot-loader layer not being found, reliably, in a Azure DevOps build (which seems to use, these days, the same underlying engine as the public github infrastructure). Strangely, in one build definition it reliably works, and the exact same Dockerfile run in a second one doesn't, and the build output of the failed one, if downloaded and run against the Dockerfile, does work. I'm starting to think the issue is something on Microsoft's side, not in Docker or Spring's layer generation, but I haven't been able to figure out how to get any more data on it. |
Nope, didn't figure it out yet. Are there any other actions that can do similar thing? |
Same here |
So I actually figured this out. It seems to be a timing-related thing. Add a "RUN true" between each copy step. So: COPY ... etc That fixed it reliably for me. |
Hi, Can you try with the future build-push-action v2 (#92)? |
Seems to have the same error, take a look https://github.com/AndriyKalashnykov/spring-microservices-k8s/runs/1062414050?check_suite_focus=true |
@AndriyKalashnykov Inputs have changed in v2. See Usage section and also this workflow as an example. |
Version 2 has been merged to the main branch and is therefore available via As a reminder, this new version changes drastically and works with 3 new actions (login, setup-buildx and setup-qemu) that we have created. Many usage examples have been added to handle most use cases. And it should fix this current issue. Don't hesitate if you have any questions. |
When running build-push-action - specifically this workflow run
on multi-stage Docker image following error occurs:
The text was updated successfully, but these errors were encountered: