@@ -46,18 +46,18 @@ RUN echo "deb http://deb.debian.org/debian bullseye-backports main" >> /etc/apt/
4646# Add alias until env variables will be supported by crowdsec.
4747RUN echo 'alias cscli="cscli -c /config/.storage/crowdsec/config/config.yaml"' > /root/.bashrc
4848
49- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec /etc/crowdsec
50- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/var/lib/crowdsec /var/lib/crowdsec
51- COPY --from=crowdsecurity/crowdsec:v1.6.6 /usr/local/bin/crowdsec /usr/local/bin/crowdsec
52- COPY --from=crowdsecurity/crowdsec:v1.6.6 /usr/local/bin/cscli /usr/local/bin/cscli
53- COPY --from=crowdsecurity/crowdsec:v1.6.6 /docker_start.sh /docker_start.sh
54- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/config.yaml /etc/crowdsec/config.yaml
49+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec /etc/crowdsec
50+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/var/lib/crowdsec /var/lib/crowdsec
51+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /usr/local/bin/crowdsec /usr/local/bin/crowdsec
52+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /usr/local/bin/cscli /usr/local/bin/cscli
53+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /docker_start.sh /docker_start.sh
54+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec/config.yaml /etc/crowdsec/config.yaml
5555# Due to the wizard using cp -n, we have to copy the config files directly from the source as -n does not exist in busybox cp
5656# The files are here for reference, as users will need to mount a new version to be actually able to use notifications
57- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/notifications/email.yaml /etc/crowdsec/notifications/email.yaml
58- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/notifications/http.yaml /etc/crowdsec/notifications/http.yaml
59- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/notifications/slack.yaml /etc/crowdsec/notifications/slack.yaml
60- COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/notifications/splunk.yaml /etc/crowdsec/notifications/splunk.yaml
57+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec/notifications/email.yaml /etc/crowdsec/notifications/email.yaml
58+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec/notifications/http.yaml /etc/crowdsec/notifications/http.yaml
59+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec/notifications/slack.yaml /etc/crowdsec/notifications/slack.yaml
60+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /staging/etc/crowdsec/notifications/splunk.yaml /etc/crowdsec/notifications/splunk.yaml
6161# This is an ugly workaround for an issue reported on discord
6262# The container fails to start with the error "ln: failed to create symbolic link '/var/lib/crowdsec/data/*': File exists"
6363# In the HA container, /staging/var/lib/crowdsec/data/ does not exist, and the crowdsec docker_start.sh script loops
@@ -68,7 +68,7 @@ COPY --from=crowdsecurity/crowdsec:v1.6.6 /staging/etc/crowdsec/notifications/sp
6868RUN mkdir -p /staging/var/lib/crowdsec/data/ && touch /staging/var/lib/crowdsec/data/crowdsec.db
6969# workaround to avoid having build issue ("failed to create image: failed to get layer")
7070RUN true
71- COPY --from=crowdsecurity/crowdsec:v1.6.6 /usr/local/lib/crowdsec/plugins /usr/local/lib/crowdsec/plugins
71+ COPY --from=crowdsecurity/crowdsec:v1.6.8 /usr/local/lib/crowdsec/plugins /usr/local/lib/crowdsec/plugins
7272
7373# Copy root filesystem
7474COPY rootfs /
0 commit comments