Skip to content
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

vulneribilities found in docker scout for nightly-20241028 #19165

Open
cyliu0 opened this issue Oct 29, 2024 · 0 comments · May be fixed by #19208
Open

vulneribilities found in docker scout for nightly-20241028 #19165

cyliu0 opened this issue Oct 29, 2024 · 0 comments · May be fixed by #19208
Labels
type/bug Something isn't working
Milestone

Comments

@cyliu0
Copy link
Collaborator

cyliu0 commented Oct 29, 2024

Describe the bug

https://buildkite.com/risingwavelabs/docker/builds/16532#0192d300-4d16-4b32-9541-7fbc3f6b28b5


Target             │  ghcr.io/risingwavelabs/risingwave:0d013eab1bba8cd86c575057e165586262362636-x86_64  │   24C    58H   461M    43L
--
  | digest           │  b6cbad48a260                                                                       │
  | Base image         │  ubuntu:24.04                                                                       │    0C     0H     1M     4L
  | Updated base image │  ubuntu:24.10                                                                       │    0C     0H     0M     0L
  | │                                                                                     │                  -1     -4

The detailed cves listed https://buildkite.com/risingwavelabs/docker/builds/16532#0192d300-4d16-4b32-9541-7fbc3f6b28b5/196

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

nightly-20241028

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant