Open mattiaspalm opened 6 years ago
@mattiaspalm I think it's related to how Caddy may be packaging their files. I rewrote the Dockerfile for the proxy here that uses the install script getcaddy.com, which may or may not be a deal-breaker for you, but works around this issue:
https://github.com/seanlane/docker-ghost-caddy/blob/master/proxy/Dockerfile
@seanlane Hi, thanks for forking and updating!
I'm trying to run docker-compose build
using your repo but it looks like getcaddy is broken since Caddy v2.
Do you know how I could adapt to this work with Caddy v2?
@steakscience Hi, I updated my fork to use a Docker image with Caddy 2, so you should be able to build it now: https://github.com/seanlane/docker-ghost-caddy
Hi, I have changed CaddyFile and url in the docker-compose, got this when trying to build:
(10/10) Installing tar (1.29-r1) Executing busybox-1.26.2-r9.trigger Executing ca-certificates-20161130-r2.trigger OK: 28 MiB in 21 packages curl: (22) The requested URL returned error: 400 Bad Request gzip: invalid magic tar: Child returned status 1 tar: Error is not recoverable: exiting now ERROR: Service 'proxy' failed to build: The command '/bin/sh -c apk add --no-cache openssh-client git tar curl && curl --silent --show-error --fail --location --header "Accept: application/tar+gzip, application/x-gzip, application/octet-stream" -o - "https://caddyserver.com/download/linux/amd64?plugins=${plugins}" | tar --no-same-owner -C /usr/bin/ -xz caddy && chmod 0755 /usr/bin/caddy && /usr/bin/caddy -version' returned a non-zero code: 2