You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dotnet 6.0 applications behave as they should and when we upgraded to dotnet 8 we see this error.
Current Behavior
unexpected EOF ERROR: failed to build: exit status 1 ERROR: failed to build: executing lifecycle: failed with status code: 51
Possible Solution
Maybe it has something to do with running docker-in-docker (with the pack cli) inside a kubernetes cluster (the gitlab runners run in the kubernetes cluster). I know its very complex ;-) We rooted out OOM in the pods.
Steps to Reproduce
I know its hard to reproduce. We are hoping for some guidance into further investigating this bug. I am also willing to submit PRs with a solution is possible.
Let me know if you want me to add further info!
The text was updated successfully, but these errors were encountered:
msthtrifork
changed the title
dotnet publish fails (dotnet 8.0)
dotnet SDK fails (dotnet 8.0)
Oct 9, 2024
When running the pack cli with the paketo builder with a dotnet 8.0 application in a Gitlab CI environment we (sometimes) get the following error:
The error is:
The most frustrating thing is that this error appears maybe every 2-3 builds, sometimes everything works and the image is built.
We don't get any more info of the error when running with:
What can "unexpected EOF" mean in this instance?
Expected Behavior
Dotnet 6.0 applications behave as they should and when we upgraded to dotnet 8 we see this error.
Current Behavior
unexpected EOF ERROR: failed to build: exit status 1 ERROR: failed to build: executing lifecycle: failed with status code: 51
Possible Solution
Maybe it has something to do with running docker-in-docker (with the pack cli) inside a kubernetes cluster (the gitlab runners run in the kubernetes cluster). I know its very complex ;-) We rooted out OOM in the pods.
Steps to Reproduce
I know its hard to reproduce. We are hoping for some guidance into further investigating this bug. I am also willing to submit PRs with a solution is possible.
Let me know if you want me to add further info!
The text was updated successfully, but these errors were encountered: