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
Chore: switch to go mod compatible fork of forego #1603
Conversation
94b8f87
to
d068fd6
Compare
@tkw1536 well that's back to the drawing board on this one, the forego version built by alpine fails. |
I have no idea why the tests fail on alpine. The logs seem to imply that the container just crashes, but I can not reproduce this locally. I have a strong suspicion that the changes could be caused by any of the commits introduced since v0.16.1. I will see when I have the time to investigate in more detail. |
That's appreciated 👍 No pressure / hurry though, I think we should be fine staying on Go < |
It's been a while, but I finally got around to tracking why this happens.
But I don't know why this happens only on Alpine and not on Debian. |
Ok, I've figured out what the problem is, the default shell under alpine does not seem to support all the features introduced in ddollar/forego@51d9f6d. |
Going to do some minor cleanup on forego, and then make a PR. |
Excellent news, thanks @tkw1536 ! 👍 |
See nginx-proxy/forego#2, we'll need to update this PR as well. |
Do you recommend using |
Well, both |
As discussed in #1579, forego isn't maintained anymore and lacks go module support. This project was already using a fork of forego by jwilder, so I decided to fork it again under the nginx-proxy org and merge in go mod support (thanks to @tkw1536) so that it can be used in this project and unblock building the image with golang >=
1.16
.