Crowdsec with Jellyseerr

iiAmLoz · January 30, 2024, 4:30pm

Yes it bad practice to mount the socket directly into the container, I wrote a example within our docker compose repo

crowdsecurity/example-docker-compose/blob/35f7dd0ca45e7643697e15edd21a6270a2226080/container-socket/docker-compose.yml#L22-L70


      
          crowdsec:
            image: crowdsecurity/crowdsec
            restart: always
            networks:
              crowdsec:
            ports:
              - "127.0.0.1:8080:8080"
            environment:
              ## DOCKER_HOST: tcp://socket-proxy:2375
              COLLECTIONS: "crowdsecurity/nginx"
            depends_on:
              - 'reverse-proxy'
            volumes:
              ## Bad pratice to mount docker socket into a container
              - /var/run/docker.sock:/var/run/docker.sock:ro
              ######################################################
              - ./crowdsec/acquis.yaml:/etc/crowdsec/acquis.yaml
              - crowdsec-db:/var/lib/crowdsec/data/
              - crowdsec-config:/etc/crowdsec/

This file has been truncated. show original

So you un-comment the socket proxy container and the ## DOCKER_HOST: tcp://socket-proxy:2375

This example is for a root docker installation, if your using rootless docker then the path if different.

Topic		Replies	Views
Issues with running on Docker crowdsec	1	1468	February 18, 2022
Running crowdsec as non-root user in Docker? crowdsec	5	1219	April 30, 2026
Docker log source with socket proxy crowdsec	1	1019	November 6, 2024
Have CrowdSec container read journald messages from host crowdsec	4	3206	July 1, 2023
Issues setting up crowdsec on docker with traefik crowdsec	2	1229	August 1, 2025

Crowdsec with Jellyseerr

Related topics