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
The API Platform Dockerfile uses 2.6.4 of Caddy:
RUN xcaddy build v2.6.4 \ --with github.com/dunglas/mercure/caddy \ --with github.com/dunglas/vulcain/caddy
This results in building caddy with the latest version of mercure - v0.15.1 - but this release requires v2.7 of Caddy.
caddy
mercure
Docker container builds fail with the following:
6.092 2023/08/04 14:44:31 [INFO] exec (timeout=-2562047h47m16.854775808s): /usr/local/go/bin/go get -d -v github.com/dunglas/mercure/caddy github.com/caddyserver/caddy/v2@v2.6.4 6.369 go: downloading github.com/dunglas/mercure v0.15.1 6.370 go: downloading github.com/dunglas/mercure/caddy v0.15.1 6.969 go: github.com/dunglas/mercure/caddy@upgrade (v0.15.1) requires github.com/caddyserver/caddy/v2@v2.7.2, not github.com/caddyserver/caddy/v2@v2.6.4 6.970 2023/08/04 14:44:32 [FATAL] exit status 1
Should the API Platform Dockerfile be pinned to use a specific version of Mercure for the 2.6.4 build?
Mercure
2.6.4
The text was updated successfully, but these errors were encountered:
This has been fixed in recent API Platform versions: api-platform/api-platform#2452 (comment)
To fix this issue, you can either switch to the new method to install Caddy (better), or change v2.6.4 by v2.7.2.
v2.6.4
v2.7.2
The API Platform Dockerfile uses 2.6.4 of Caddy:
This results in building
caddy
with the latest version ofmercure
- v0.15.1 - but this release requires v2.7 of Caddy.Docker container builds fail with the following:
Should the API Platform Dockerfile be pinned to use a specific version of
Mercure
for the2.6.4
build?The text was updated successfully, but these errors were encountered: