Skip to content

fix: too many vulnerabilities - Trigger new build #2

Description

@mmornati

Problem

The latest built (and available) image is having a lot of vulnerabilities (related to the May NGINX image).
image

Fix

As the Dockerfile is using the latest nginx:alpine (latest at the build time), simply triggering a new build (and creating a new version) will fix most of the vulns.
image

Improvements

A possible improvement (to prevent any manual operation) is to trigger a new minor image release each time nginx is releasing a new image.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions