breadsmasher, 1 year ago

When you tried caddy and received an error, that looks like you are getting the wrong image name.

Then you mentioned deleting caddyfile as the configuration didn’t work. But, if I am following correctly the caddyfile wouldn’t yet be relevant if the caddy container hadn’t actually ran.

Pulling from Caddys docs, you should just need to run

<span style="color:#323232;">$ docker run -d -p 80:80 
</span><span style="color:#323232;">    -v $PWD/Caddyfile:/etc/caddy/Caddyfile 
</span><span style="color:#323232;">    -v caddy_data:/data 
</span><span style="color:#323232;">    caddy
</span>

Where $PWD is the current directory the terminal is currently in.

Further docs for then configuring for HTTPs you can find here under

Automatic TLS with the Caddy image

hub.docker.com/_/caddy