I would be interested in this. I used crowdsec+caddy through Opnsense firewall, liked it.
services:
caddy:
build:
context: .
dockerfile: Containerfile
container_name: caddy
restart: always
security_opt:
- no-new-privileges=true
cap_add:
- NET_ADMIN
environment:
CROWDSEC_API_KEY: "${CROWDSEC_API_KEY}"
ports:
- 80:80
- 443:443
- 443:443/udp
networks:
- webproxy
- crowdsec
volumes:
- ./config/caddy:/etc/caddy
- ./data/caddy:/data
- logs:/var/log/caddy
command: run --config /etc/caddy/Caddyfile
crowdsec:
image: crowdsecurity/crowdsec
restart: unless-stopped
security_opt:
- no-new-privileges=true
environment:
GID: "${GID:-1000}"
COLLECTIONS: crowdsecurity/caddy crowdsecurity/http-cve crowdsecurity/whitelist-good-actors
BOUNCER_KEY_CADDY: "${CROWDSEC_API_KEY}"
networks:
- crowdsec
volumes:
- crowdsec-db:/var/lib/crowdsec/db
- ./config/crowdsec/acquis.yaml:/etc/crowdsec/acquis.yaml
- logs:/var/log/caddy:ro
networks:
crowdsec:
webproxy:
name: webproxy
volumes:
logs:
crowdsec-db:Alles anzeigencap_add:
- NET_ADMIN
-------
ports:
- 80:80
- 443:443
- 443:443/udp
Using these on a container will clash with OMV GUI if you don't change the web port the workbench uses to something other then 80
I can't find any documentation that describes this specific situation...
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
