-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Enforce osusergo build tag for releases #6862
Conversation
@sapk are you able to reproduce this problem? We need to ensure that the issue is solved by this addition. |
Codecov Report
@@ Coverage Diff @@
## master #6862 +/- ##
==========================================
- Coverage 41.18% 41.17% -0.01%
==========================================
Files 425 425
Lines 58490 58490
==========================================
- Hits 24091 24086 -5
- Misses 31212 31216 +4
- Partials 3187 3188 +1
Continue to review full report at Codecov.
|
@zeripath I can't reproduce the bug exactly since I don't know (yet) which glib is incompatible with which glib version but the output of the linker go in this direction :
The released gitea 1.8 binary seems to work on the docker image debian:9.6. I will try to find a tag that doesn't work. |
I've been trying to find the broken version too... I think it's libc6 2.26 but I don't know which version of debian has that. |
hmm... Is it possible that this might fix the static build problems for Arm7 might be fixed by osusergo too? |
On the docker image 9.6 it is libc6 2.24 |
ubuntu:bionic has 2.27-3ubuntu1 and works |
For testing, I use :
|
17.10 works even though its version is 2.26-0ubuntu2.1 |
so Now the arm7 build from that still doesn't work - it just gives me an illegal instruction. |
@zeripath what warning do you got that where remove with static_build ? unixDlOpen was the only I still got using only netgo and osusergo. |
oh sorry I'm talking nonsense. I misread your message earlier. And I've misunderstood how the suggestion was working - the static_build tag must have been internal to that particular commenter's build. |
@sapk why don't you come to discord and we can chat a bit more without spamming this |
I've decided to approve even though we can't prove that this will solve the problem. Unfortunately it looks like this doesn't solve the arm7 problem (at least on pi2) |
So this will need to be backported to 1.8 in order for us to fix the issue. |
@zeripath done |
Similar to #1690, we need a new tag to use the go version and not the linked cgo version that fail on some distrib. In this case, we are using it to finding the runnning user.
Should fix #6841 and also reported bug on discourse