-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix for the failing CD build #646
Conversation
cdf13b0
to
767a5dc
Compare
@schollz , Can you please review and approve this PR? |
Hello @rehanone, I have the same problem when building the image for the 386 architecture locally because it requires
Instead of removing the arm and 386 builds, the problem can be fixed by installing the |
730f4be
to
e1e46c8
Compare
e1e46c8
to
9ad2af1
Compare
@gfieni , Thanks for the tip! It looks like with your suggested changes, all platform images are building as expects! I have updates the PR to reflect those updates and it is ready for review. |
@schollz , Can you please provide feedback on this PR? I am concerned about the security of the current docker images as they almost 2 years old now. Hopefully, if this PR fixes the build issue then everyone who uses docker image as a relay would have a newer image. |
sounds good! |
What about the .deb targets? It seems they no longer get released. |
@pepa65 you can add the .deb targets you want into the new release.yml: https://github.com/schollz/croc/blob/main/.github/workflows/release.yml. I'll accept the pr |
Hmm, no more goreleaser... It's not immediately clear to me how to add this in. I will wait for someone to pick this up. In the meantime, I am happy to just get the binaries I need, which is what I love about go and croc! |
Unfortunately #645 still failed to publish the latest artifacts to DockerHub. The issue does not happen in local testing which leads me to believe it is to do with the legacy architectures. The logs of the failure also indicate in that direction.
I have disabled the legacy 386 and 32-bit arm build in this fix to get the normal images published. Perhaps a more detailed analysis and fix would be required for enabling the legacy builds again. The problem seams to be around these flags
-ldflags="-s -w"
Also It looks like the CI build is using the go version 1.20 so I bumped that to be consistent.