Repository navigation
COLLECTIONS env variable is ignored by crowdsec-agent #322
Description
Activity
@hanspaerna: Thanks for opening an issue, it is currently awaiting triage.
If you haven't already, please provide the following information:
- kind :
bug,enhancementordocumentation - area :
agent,appsec,configuration,cscli,local-api
In the meantime, you can:
- Check Crowdsec Documentation to see if your issue can be self resolved.
- You can also join our Discord.
- Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.
- kind :
@hanspaerna: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind bug/kind documentation/kind enhancement
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.
the custom startup is only used for the LAPI pods (according to note at top of file :D ), where are you defining this environment as it should be only applied to
agentcontainers and notLAPI?## formatting is probably broken but just for reference agent: env: - name: COLLECTIONS value: "crowdsecurity/linux"
Ah, so the custom startup script is not involved into this at all. I'm actually setting the COLLECTIONS env to crowdsec-agent pod, not LAPI. I can show you a piece of the manifest that I create with Kustomize patches and deploy:
spec: selector: matchLabels: k8s-app: crowdsec type: agent template: metadata: annotations: ... labels: k8s-app: crowdsec type: agent version: v1 spec: containers: - name: crowdsec-agent image: crowdsecurity/crowdsec:v1.7.4 command: - sh - -c - cp /tmp_config/local_api_credentials.yaml /staging/etc/crowdsec/local_api_credentials.yaml && ./docker_start.sh env: - name: DISABLE_LOCAL_API value: "true" - name: DISABLE_ONLINE_API value: "true" - name: CROWDSEC_BYPASS_DB_VOLUME_CHECK value: "true" - name: LOCAL_API_URL value: http://crowdsec-service.crowdsec:8080 - name: COLLECTIONS value: crowdsecurity/traefikOn the other hand, if the generated manifest has the variable declared in a right place, then this might be a problem with the Docker image itself.
After deploying what are the pod logs cause the the image will print out all the startup logs (including downloading the hub items from env)
Hi. I've inspected the source of docker-start.sh and environment variables inside a deployed crowdsec-agent pod, and couldn't find any indications of this value being processed and used anyhow. Setting it has no effect on a list of installed collections.
/kind bug
/area agent