how to handle redeployment?
I get the following message, upon redeploying my docker swarm (with a single node).
level=warning msg="Instance already enrolled. You can use '--overwrite' to force enroll"
Is it recommended to overwrite?6 Replies
Important Information
Thank you for getting in touch with your support request. To expedite a swift resolution, could you kindly provide the following information? Rest assured, we will respond promptly, and we greatly appreciate your patience. While you wait, please check the links below to see if this issue has been previously addressed. If you have managed to resolve it, please use run the command
/resolve or press the green resolve button below.Log Files
If you possess any log files that you believe could be beneficial, please include them at this time. By default, CrowdSec logs to /var/log/, where you will discover a corresponding log file for each component.
Guide Followed (CrowdSec Official)
If you have diligently followed one of our guides and hit a roadblock, please share the guide with us. This will help us assess if any adjustments are necessary to assist you further.
Screenshots
Please forward any screenshots depicting errors you encounter. Your visuals will provide us with a clear view of the issues you are facing.
© Created By WhyAydan for CrowdSec ❤️
this means the configuration directory is most likely persisted and it should be the same engine that is already enrolled in your account
this means the configuration directory is most likely persistedThat is correct. What you mean with that?
it should be the same engine that is already enrolled in your account
Resolving how to handle redeployment?
This has now been resolved. If you think this is a mistake please run
/unresolve
Unresolving how to handle redeployment?
This has now been unresolved.Since the configuration directory is persisted, the engine upon redeployment isnt classed as a new engine so if you enrolled it, then its seen as the same engine
First, thank you @Loz ❤️
This is exactly what I want.
Would there be a reason why I shouldn't do or want that?
Anything else I should look out for when doing it this way (keeping the old configuration when updating my container)?
Afterall this message has log level warning and not info.
So maybe it might not always work?
Is it fine to keep the configuration around when updating https://github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin
or crowdsec https://hub.docker.com/r/crowdsecurity/crowdsec ?
GitHub
GitHub - maxlerebourg/crowdsec-bouncer-traefik-plugin: Traefik plug...
Traefik plugin for Crowdsec - WAF and IP protection - maxlerebourg/crowdsec-bouncer-traefik-plugin