-
Notifications
You must be signed in to change notification settings - Fork 316
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
Build with custom plugins fails to use new plugins list as a build argument #77
Comments
Firstly, change Then can you narrow down the list of plugins to see which ones failed to build. |
I've narrowed it down. proxyprotocol and locale are not getting picked up due to a bug in caddyplug, the tool being used to detect packages for plugins. This is within my control and I can work on a fix. grpc is failing to build with the following error, this is outside my control.
For now, omit forwardproxy, locale and grpc and you should have a successful build. The other option is https://caddyserver.com/download which only builds with stable version of the plugins. There is no way outside of Caddy dashboard to track stable plugin versions, so all builds are done off master. |
Thanks for looking into this. The weird thing is that I get the same results when I skip compose and just use your example snippet:
Here's the full output of that command in case it helps:
|
Something is probably wrong with your environment. Can you tear down compose and try again or use another environment and I have no issues building with custom plugins. |
This seems to be an issue with the way that the build process interacts with the environment on my Synology NAS. I was able to build on a different machine and then use that image as the source on my NAS without issue. Thanks for your help. |
Sorry for reanimating old issue - fix for grpc was relatively simple: pieterlouw/caddy-grpc#2 Edit:
|
The instructions for building a custom image with a user specified plugin list no longer work with the recent updates to the builder.
I've also tried using the instructions in the readme for a one time build separate from my compose file, and those did not change the plugins installed. These instructions use the new plugin format that was called out in my original issue #76
This section in a compose file used to work perfectly for building a new image with my desired plugins:
Now the image builds, but the verification step lists only standard plugins, and doesn't include any of the extras requested.
The text was updated successfully, but these errors were encountered: