Skip to content
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

Error "failed to write payload" in distroless image #24

Open
Tobias-08 opened this issue Jul 11, 2024 · 5 comments
Open

Error "failed to write payload" in distroless image #24

Tobias-08 opened this issue Jul 11, 2024 · 5 comments

Comments

@Tobias-08
Copy link

Hi,

we are using godartsass in Corteza. It works as expected in a Debian based image. But while trying to setup a distroless based image with a nonroot user godartsass fails in the transpiler on line 536 with error failed to write payload (the internal error is broken pipe).

This seems to be a godartsass and not a Corteza issue. Does anyone have a hint what in distroless is missing (dependencies? permissions? ...?) and stops godartsass from working?

Thanks!

@Tobias-08 Tobias-08 changed the title Error "failed to wirte payload" in distroless image Error "failed to write payload" in distroless image Jul 11, 2024
bep added a commit that referenced this issue Jul 11, 2024
bep added a commit that referenced this issue Jul 11, 2024
bep added a commit that referenced this issue Jul 11, 2024
@bep
Copy link
Owner

bep commented Jul 11, 2024

I have pushed a v2.1.0 with this commit 658e28a

Note that I'm pretty sure you still will get an error, but the error should provide more context.

I have not seen that error "in the wild" before, and this library has been pretty good battle tested in Hugo.

@Tobias-08
Copy link
Author

@bep Thanks for your quick response and your effort for investigating this issue further.

I hope that I can give v2.1.0 a try tomorrow.

@Tobias-08
Copy link
Author

@bep Now tried v2.1.0. Error output is:

{"error": "failed to write payload: write |1: broken pipe"}
{"error": "connection is shut down"}

Perhaps not as detailed/helpful as you were looking for...?

@bep
Copy link
Owner

bep commented Jul 12, 2024

Perhaps not as detailed/helpful as you were looking for...?

This can be related to how you handle the transpiler instances, so I suggest you fix that first (I created an issue).

@Tobias-08
Copy link
Author

cortezaproject/corteza#1860 does not seem to have helped. Same behaviour as before ("connection is shut down").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants