-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Building caddy (using xcaddy) with main branch throws an error #5301
Comments
Weird. It works in CI for us, obviously. Apparently there's some issues with this upstream golang/go#56494
|
Definitely seems related :( Was able to build with 817470d at least. |
That's weird... I am not able to see that behavior either... The panic is definitely coming from within |
No worries, I wasn't aware this is an upstream bug. Hope this gets solved soon. I even tried Fedora Rawhide but still no luck :( |
I ran into this a couple of times. I'm not entirely what's going on, but I did manage to get it to compile. I'm compiling Caddy with several plugins and had them in alphabetical order: ./xcaddy build latest \
--with github.com/caddy-dns/alidns \
--with github.com/caddy-dns/azure \
--with github.com/caddy-dns/cloudflare \
--with github.com/caddy-dns/digitalocean \
--with github.com/caddy-dns/dnspod \
--with github.com/caddy-dns/duckdns \
--with github.com/caddy-dns/gandi \
--with github.com/caddy-dns/hetzner \
--with github.com/caddy-dns/namecheap \
--with github.com/caddy-dns/netlify \
--with github.com/caddy-dns/ovh \
--with github.com/caddy-dns/porkbun \
--with github.com/caddy-dns/route53 \
--with github.com/caddy-dns/scaleway \
--with github.com/caddy-dns/vercel \
--with github.com/caddy-dns/vultr \
--with github.com/caddy-dns/godaddy \
--with github.com/caddy-dns/googleclouddns I was getting the same error with I tried commenting out No idea why and I'm not very familiar with Go, but I thought I'd mention that I ran into the same thing. Maybe it's an issue with one of these DNS plugins? |
Running into the same issue with |
I get the error with that command too, @onodera-punpun -- unfortunately, this is an upstream issue in the Based on user reports above, it seems like the order of dependencies in go.mod matters (which it shouldn't), and I wonder if the dependencies of the plugins (i.e. their go.mod files) matters; like maybe if they're targeting older versions of Caddy or even Go. I dunno. |
I did some investigating, that I outlined here golang/go#56494 (comment). I have no solution right now 😬 |
@excid3 @onodera-punpun FYI I've figured out that the issue can be fixed by the plugins bumping their Caddy dependency in their This problem really shouldn't have happened. Go's module system is still proving to not be quite robust enough. We keep running into little issues like this and it feels like there's rarely much we can do. |
Very interesting. Thanks for looking into this @francislavoie. 👍 Are the caddy-dns modules updated? |
@excid3 The caddy-dns modules are independently maintained. It's not clear to me which plugins need updating yet. For example, |
I have the same problem. I'm building caddy with this docker file:
And I get the same error. This should be easy to reproduce. Is there any workaround I can do to keep using godaddy? |
@mario-moreira This is very convoluted but I was able to get your build to work with:
Do not ask me why. 🤷♂️ |
@mholt yes, it worked. Problem solved for the moment. Thank you. |
@mholt this was working fine until today. Can no longer build it again even with your fix:
Sorry about the ping matt. Turns out an upstream: /caddy-dns/route53/releases had a new release which for some reason broke it again. Downgrading to So now im going and hard locking all deps (probably a good thing anyway but pain in the ass to upgrade) |
We are hoping the Go team fixes the bug ASAP. |
Following up with the discussion in the main caddy project, plugins should update their dependencies to avoid build issues. caddyserver/caddy#5301 (comment)
Commit that seems to cause this is 798c4a3 as that's when google/pprof was added
panic: internal error: can't find reason for requirement on github.com/google/pprof@v0.0.0-20210407192527-94a9f03dee38
Go version:
go version go1.19.4 linux/amd64
(Fedora 37) andgo version go1.19.5 linux/amd64
(Arch Linux)Error happens on both distros
The text was updated successfully, but these errors were encountered: