# Changes to the Docker image tag naming convention

**URL:** <https://forum.flow.com/t/changes-to-the-docker-image-tag-naming-convention/5568>\
**Category:** Node Operations\
**Created:** [January 9, 2024, 8:22pm UTC](https://forum.flow.com/t/changes-to-the-docker-image-tag-naming-convention/5568 "2024-01-09T20:22:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [January 9, 2024, 8:22pm UTC](https://forum.flow.com/t/changes-to-the-docker-image-tag-naming-convention/5568/1 "2024-01-09T20:22:38Z")

</div>

hello node operators,

The naming convention for the `without-netgo` images will be changed slightly.  
Instead of the docker image being tagged as `v0.x.x-without-netgo`, it will be tagged as `v0.x.x+without-netgo`, a `+` instead of a `-`.

e.g. `v0.32.11-without-netgo` becomes `v0.32.11+without-netgo`

or `v0.32.11-patch.1-without-netgo` becomes `v0.32.11-patch.1+without-netgo`

For more details and the reason for this change, see the PR: [[CI] Use build tag for without-netgo by peterargue · Pull Request #5157 · onflow/flow-go · GitHub](https://github.com/onflow/flow-go/pull/5157).

Feel free to leave any comments/feedback directly on the PR.

_This will only apply to new images built going forward._

Thank you,  
Flow Team