1. The problem I’m having:
I was using Caddy to expose one service and it worked well, now I wanted to expose a new service, using duckdns (I was using no-ip before but I didn’t find the plugging )
So after a lot of reading, I changed my compose file and I build caddy with duckdns plugging to get everything work, but since that, It doesn’t work at all, and I don’t have almos any log in the output, so now I’m not sure if building was succesfull (even if I didn’t have any error message)
2. Error messages and/or full log output:
Apparently no error messages
[+] Running 1/1
✔ Container caddy-caddy-1 Created 0.0s
Attaching to caddy-1
caddy-1 exited with code 0
caddy-1 exited with code 0
caddy-1 exited with code 0
caddy-1 exited with code 0
caddy-1 exited with code 0
3. Caddy version:
v2.9.1 h1:OEYiZ7DbCzAWVb6TNEkjRcSCRGHVoZsJinoDR/n9oaY=
4. How I installed and ran Caddy:
a. System environment:
Docker container running in a raspberry pi
b. Command:
sudo docker compose up -d
c. DockerFile file:
FROM caddy:builder AS builder
RUN xcaddy build \
--with github.com/caddy-dns/duckdns
FROM caddy:builder
COPY --from=builder /usr/bin/caddy /usr/bin/caddy
c. docker-compose file:
services:
caddy:
build: .
restart: unless-stopped
ports:
- "82:80"
- "443:443"
- "443:443/udp"
volumes:
- ./data/:/data/
- ./config/:/config/
- ./Caddyfile:/etc/caddy/Caddyfile
- caddy_data:/data
- caddy_config:/config
volumes:
caddy_data:
caddy_config:
d. My complete Caddy config:
{
email myhost@gmail.com
debug
}
immich.myhost.duckdns.org {
tls {
dns duckdns mytoken
}
reverse_proxy 192.168.1.18:2283
}
traccar.myhost.duckdns.org {
tls {
dns duckdns mytoken
}
reverse_proxy 192.168.1.18:8082
}