1. My Caddy version (caddy -version): docker caddy/caddy:alpine 2. How I run Caddy: Please provide all of the relevant information and DO NOT REDACT anything except passwords/keys. Thank you! a. System environment: OS, relevant versions, systemd? docker? etc. Ubuntu 1804 docker 19.0.3 b. Comman…

Looks like you got the help you needed here! Config and data are not persisted even though I am mounting volumes · Issue #42 · caddyserver/caddy-docker · GitHub

When you run containers using docker-compose, it adds hosts for each of your services to the docker network’s DNS server. These hosts are the service name by default. In your case, this would be perceptionist and bratsstarz. I think that the container_name option will override that, so I think you m…

Thank you I am confident I will figure the routing out. But how to handle the certificate error? Outside the docker getting the cert works fine, but inside I get the errors above.

Ah, I think that’s because you’re overriding the CA store with your ./caddy_secrets/ssl/:/etc/ssl volume, which means that Caddy doesn’t know how to trust the Let’s Encrypt CA.

Ah that folder does not exist when I start the docker, so it gets created in the process. I also tried without this volume mount. But will try again.

I tried again with the following settings…maybe it fails now because I tried too often in the last hours? I think the cert files should be somehow volume mounted to avoid caddy getting new certs, every time the docker restarts? Caddyfile: { email ****@gmail.com } translatum.spdns.org www.…

In v2, the paths you need to persist are /root/.config/caddy and /root/.local/share/caddy, assuming you’re running the docker image with the root user. See Conventions — Caddy Documentation See below, the new paths are /data and /config in the latest Docker images.

Just a note - as of the latest caddy/caddy images, these locations are now /config/caddy and /data/caddy. See the (new!) docs for some details: GitHub - caddyserver/caddy-docker: Source for the official Caddy v2 Docker Image

Thanks for the headsup just resumed work on my project! Hope I will get it running now!

Alright I moved on with the project and made some small progress. Accessing the base route with ssl cert works, but the proxy to my nginx backend working on 8080 does not: docker-compose # run this with: " CURRENT_UID=$(id -u):$(id -g) docker-compose up "" version: "3" services: percy: # do…

I found it the port was still mapped to 8080 as I remapped my docker there but nginx usually is served on 80 :slightly_smiling_face: now I only need to get my backend running

Caddy Community

How to run Caddy v2 inside a docker container and reverse proxy between docker containers?

Help