Skip to content
Docker Security Scan

Docker Security Scan #256

Sign in to view logs

Docker Security Scan

Docker Security Scan #256

Triggered via schedule April 27, 2026 08:03
@josecelanojosecelano
⁠ c536c53
main
Status Failure
Total duration 5m 0s
Artifacts 8

docker-security-scan.yml

on: schedule
Matrix: Scan Project-Built Docker Images
Extract Third-Party Docker Images from Source
1m 19s
Extract Third-Party Docker Images from Source
Upload SARIF Results to GitHub Security
22s
Upload SARIF Results to GitHub Security
Matrix: Scan Third-Party Docker Images
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 10 warnings
Scan Third-Party Docker Images (grafana/grafana:13.0.0)
Path does not exist: trivy.sarif
Scan Third-Party Docker Images (grafana/grafana:13.0.0)
Process completed with exit code 1.
Scan Project-Built Docker Images (docker/ssh-server/Dockerfile, docker/ssh-server, ssh-server)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Project-Built Docker Images (docker/backup/Dockerfile, docker/backup, tracker-backup)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Third-Party Docker Images (grafana/grafana:13.0.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Third-Party Docker Images (grafana/grafana:13.0.0)
No files were found with the provided path: trivy.sarif. No artifacts will be uploaded.
Scan Third-Party Docker Images (caddy:2.11.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Third-Party Docker Images (prom/prometheus:v3.11.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Third-Party Docker Images (mysql:8.4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Third-Party Docker Images (torrust/tracker:develop)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Project-Built Docker Images (docker/provisioned-instance/Dockerfile, docker/provisioned-inst...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Scan Project-Built Docker Images (docker/deployer/Dockerfile, ., deployer)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
sarif-project-deployer-24983550342 Expired
48 KB
sha256:bb90af274d1320c7b3f89c5264e8c8a0bd8647117230542115ecd47c54a0f134
sarif-project-provisioned-instance-24983550342 Expired
11.1 KB
sha256:a2d16e3d2050fccf41c317997ba42ab87b830ebd20f8a3ac54d250fea53ca9fb
sarif-project-ssh-server-24983550342 Expired
601 Bytes
sha256:d172da7ef2c13f534505a1eaa8ee54c430560f4de0cb419072e5a304679394a7
sarif-project-tracker-backup-24983550342 Expired
14.1 KB
sha256:08078db8323d4b0ced4435e2055befa9be8482f756a7bfbce8a6cdb5b7134b4a
sarif-third-party-caddy-2.11.2-24983550342 Expired
7.49 KB
sha256:0c4c591800795a4958f3692e3042d8715ecc6b6834388332ad2749bd8ef515e3
sarif-third-party-mysql-8.4-24983550342 Expired
9.06 KB
sha256:ca01982685ec4267458979544611a3d5a6c812da4377b17779d5cd53dae5e9a9
sarif-third-party-prom-prometheus-v3.11.2-24983550342 Expired
2.62 KB
sha256:4678cde8e7405a4d37e1317cb1f18edef51ac861d81d56823a4a2e180722f833
sarif-third-party-torrust-tracker-develop-24983550342 Expired
4.19 KB
sha256:f345e98b08cdd6c23f220d9ead29f3a55660590c7018c74b74dea9e63f234faf