Missing tags on dockerhub - only available is "latest"

splunk / attack_range

A tool that allows you to create vulnerable instrumented local or cloud environments to simulate attacks against and collect the data into Splunk

Apache License 2.0

2.16k stars 356 forks source link

Missing tags on dockerhub - only available is "latest" #801

Open mkolasinski-splunk opened 1 year ago

mkolasinski-splunk commented 1 year ago

Currently docker image is always pushed with single tag - latest: https://hub.docker.com/r/splunk/attack_range/tags https://github.com/splunk/attack_range/blob/develop/.github/workflows/publish-docker-image.yml#L38 This is not enough if user wants to pin particular image version.

I would like to refactor CI to build, publish and push docker image to dockerhub in single workflow, based on semantic versioning. Let me know what are your thoughts on this idea.

P4T12ICK commented 1 year ago

Yes I think this is a good idea. Then we also need to change our workflow of tagging and releasing a Attack Range version in a regular base.