fix: do not build from the same container #434
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are not cleaning up properly, and this causes leftovers to stay around when rebuilding the first time. This ends up to link objects during runtime, and giving out SIGILL like: ``` chatbot-ui-api-1 | SIGILL: illegal instruction chatbot-ui-api-1 | PC=0xa17ced m=7 sigcode=2 chatbot-ui-api-1 | signal arrived during cgo execution chatbot-ui-api-1 | instruction bytes: 0x62 0xf2 0xf5 0x8 0x3f 0xc0 0xc4 0xe1 0xf9 0x7e 0xc2 0x48 0x1 0xd0 0xf 0x92 chatbot-ui-api-1 | chatbot-ui-api-1 | goroutine 31 [syscall]: chatbot-ui-api-1 | runtime.cgocall(0x97f700, 0xc0002d6460) chatbot-ui-api-1 | /usr/local/go/src/runtime/cgocall.go:157 +0x5c fp=0xc0002d6438 sp=0xc0002d6400 pc=0x44cd3c ``` Signed-off-by: mudler <mudler@mocaccino.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are not cleaning up properly, and this causes leftovers to stay around when rebuilding the first time. This ends up to link objects during startup of the container with objects compiled with a different CPU flagset, and giving out SIGILL like:
Description
This PR might possibly alleviate #288 #86
Notes for Reviewers
Signed commits