Skip to content
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

Unable to start Caddy container #124

Closed
ker0x opened this issue Apr 2, 2021 · 5 comments · Fixed by #125
Closed

Unable to start Caddy container #124

ker0x opened this issue Apr 2, 2021 · 5 comments · Fixed by #125

Comments

@ker0x
Copy link
Contributor

ker0x commented Apr 2, 2021

Hello

I'm facing this error when running docker-compose up.

It occurs on both Ubuntu and Windows (through WSL2)

caddy_1  | goroutine 1 [running]:
caddy_1  | google.golang.org/protobuf/reflect/protoregistry.glob..func1(0x1c5a1a0, 0xc0001b3a40, 0x1c26000, 0xc0002b0d00, 0xc0001b3a40)
caddy_1  | 	google.golang.org/[email protected]/reflect/protoregistry/registry.go:54 +0x25f
caddy_1  | google.golang.org/protobuf/reflect/protoregistry.(*Files).RegisterFile(0xc000096ff0, 0x1c631e0, 0xc0001b3a40, 0x0, 0x0)
caddy_1  | 	google.golang.org/[email protected]/reflect/protoregistry/registry.go:127 +0xb72
caddy_1  | google.golang.org/protobuf/internal/filedesc.Builder.Build(0x0, 0x0, 0xc00030e600, 0x47a, 0x600, 0x800000003, 0x0, 0x1c39740, 0xc000099950, 0x1c42bc0, ...)
caddy_1  | 	google.golang.org/[email protected]/internal/filedesc/build.go:113 +0x1aa
caddy_1  | github.com/golang/protobuf/proto.RegisterFile(0x196f943, 0x8, 0x262f920, 0x2b3, 0x2b3)
caddy_1  | 	github.com/golang/[email protected]/proto/registry.go:48 +0x147
caddy_1  | github.com/dgraph-io/badger/v2/pb.init.1()
caddy_1  | 	github.com/dgraph-io/badger/[email protected]/pb/pb.pb.go:650 +0x5a
caddy_1  | panic: proto: file "pb.proto" is already registered
caddy_1  | See https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict
@DavidFeller
Copy link

DavidFeller commented Apr 2, 2021

I'm facing the same problem on MacOS.
EDIT: I both up- and downgraded caddy to 2.2.1 and 2.4-beta, but the issue seems to remain the same.
EDIT2: After disabling vulcain in Dockerfile and Caddyfile the caddy container stays alive.

@mindtechmedia
Copy link

Same here. Fresh ubuntu 20.04/docker installation

@dunglas
Copy link
Owner

dunglas commented Apr 3, 2021

It's probably related to caddyserver/caddy#3525. I'm taking a look.

@dunglas
Copy link
Owner

dunglas commented Apr 3, 2021

This PR should fix the problem: #125
Can you try if it works for you? Thanks!

@ker0x
Copy link
Contributor Author

ker0x commented Apr 5, 2021

@dunglas it works fine with the fix, thanks you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants