Hi there,
First of all, thanks for the great project!
I am currently looking to deploy crowdsec_manager inside a Proxmox LXC container (running Alpine Linux) alongside CrowdSec, rather than using a full Docker Compose stack. I prefer to run services natively or in LXC to avoid the overhead of nested containerization/OCI networks.
Currently, the stack seems highly geared towards a Dockerized environment. Would it be possible to explicitly support (or document, if it already exists) connecting crowdsec_manager directly to the CrowdSec Local API via a UNIX socket (e.g., /var/run/crowdsec/api.sock) or a direct localhost TCP connection?
Proposed Solution:
It would be incredibly helpful if the connection endpoint could be customized via an environment variable (something like CROWDSEC_LAPI_URL or CROWDSEC_SOCKET_PATH). This would allow the manager to easily communicate with a locally running CrowdSec daemon on bare metal or LXC without relying on Docker networks.
Thanks for considering this, and let me know if there is already a way to achieve this or if I can provide any testing on the LXC side!
Hi there,
First of all, thanks for the great project!
I am currently looking to deploy crowdsec_manager inside a Proxmox LXC container (running Alpine Linux) alongside CrowdSec, rather than using a full Docker Compose stack. I prefer to run services natively or in LXC to avoid the overhead of nested containerization/OCI networks.
Currently, the stack seems highly geared towards a Dockerized environment. Would it be possible to explicitly support (or document, if it already exists) connecting crowdsec_manager directly to the CrowdSec Local API via a UNIX socket (e.g., /var/run/crowdsec/api.sock) or a direct localhost TCP connection?
Proposed Solution:
It would be incredibly helpful if the connection endpoint could be customized via an environment variable (something like CROWDSEC_LAPI_URL or CROWDSEC_SOCKET_PATH). This would allow the manager to easily communicate with a locally running CrowdSec daemon on bare metal or LXC without relying on Docker networks.
Thanks for considering this, and let me know if there is already a way to achieve this or if I can provide any testing on the LXC side!