-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Image building creates invalid image on consecutive runs #26774
Comments
Thanks for the report. I can re-create this problem with the steps you've provided. I can also re-create the problem by running |
I had the same problem and was able to apply a workaround by setting
Example:
Of course this might slow down the builds and nevertheless should be fixed in paketo... EDIT: typo |
The issue has been identified by the Paketo team, and a fix is working its way through their CI system. If you are using one of the |
Gradle command
bootBuildImage
creates an invalid image on every other run. I mean, the first run creates a correct image, but whenbootBuildImage
is executed again, the created image cannot be started.Environment
Spring Boot 2.5.0, Gradle 7.0.2, osx, java 11
To reproduce:
First build and run
packsbugjava
app, and select Gradle project./gradlew build
./gradlew bootBuildImage
Paketo BellSoft Liberica Buildpack
docker run --rm packsbugjava:0.0.1-SNAPSHOT
Second build and run
./gradlew bootBuildImage
Paketo BellSoft Liberica Buildpack
docker run --rm packsbugjava:0.0.1-SNAPSHOT
If ones try to build an image again, output from the first run above will reapear, and the image will be runnable. Next image generation will again create the inavalid image, and so on. Every other generated image will be valid/invalid.
The text was updated successfully, but these errors were encountered: