-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[container] can't upgrade crowdsecurity/linux: downloaded but not installed #2779
Labels
Comments
@LaurenceJJones: Thanks for opening an issue, it is currently awaiting triage. In the meantime, you can:
DetailsI 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 BirthdayResearch/oss-governance-bot repository. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Version v1.6.0 users may get
On changing to newer tag, issue happens when the container is trying to upgraded a package that "should" exist.
Here is a patcher bash script just change the
VOLUME_NAME
to the persisted configuration volume (Also needs jq packages installed just because its easier to parse json response)Depending on your configuration you may need to run the script as sudo
What did you expect to happen?
The docker start script presumes the user will have these collections we already decided that we should just run
cscli hub upgrade
instead of individually picking onesHow can we reproduce it (as minimally and precisely as possible)?
N/A
Anything else we need to know?
No response
Crowdsec version
OS version
Enabled collections and parsers
Acquisition config
On Windows:
C:> Get-Content C:\ProgramData\CrowdSec\config\acquis.yaml
paste output here
Config show
Prometheus metrics
Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.
The text was updated successfully, but these errors were encountered: