Skip to content

Consider setting broker dockerfile base image back to latest or implement github action #2572

@olaals

Description

@olaals

Describe the improvement you would like to see
Had to set the broker base image to a specific version due to a segmentation fault with 2.1.0 (which was the latest).

We should set it back to latest, or better: implement a github action that periodically creates a pull request to bump version.

How will this change existing functionality?
No change if we go back to latest.

How will this improvement affect the current Threat Model?
https://devopsunlocked.dev/stop-using-docker-latest-tag/
We should update the version of the base image, but using latest tag is not the best practice either, it might be okay for our usecase though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    improvementImprovement to existing functionalitystaleThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions