Skip to content
Docker Vulnerability Scan

Docker Vulnerability Scan #180

Sign in to view logs

Docker Vulnerability Scan

Docker Vulnerability Scan #180

Triggered via schedule October 26, 2024 00:05
@almahmoudalmahmoud
⁠ b918eb0
devel
Status Failure
Total duration 1m 37s
Artifacts –

image-scan.yml

on: schedule
Matrix: Scan container images
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
Scan container images (tidyverse)
Process completed with exit code 1.
Scan container images (ml-verse)
Process completed with exit code 1.
Scan container images (tidyverse)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scan container images (ml-verse)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scan container images (r-ver)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scan container images (bioconductor_docker)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Scan container images (shiny)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/metadata-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/