Skip to content

[v1.6.0-xx] release binaries were built from "dirty" git state #6484

@thaJeztah

Description

@thaJeztah

Description

The v1.6.0-xxx releases were built from a dirty state

Steps to reproduce the issue

Download and extract a release;

curl -fsSL -O https://github.com/containerd/containerd/releases/download/v1.6.0-rc.1/containerd-1.6.0-rc.1-linux-amd64.tar.gz
tar -xvzf containerd-1.6.0-rc.1-linux-amd64.tar.gz

Checking the version output of various binaries (notice the .m at the end);

./bin/containerd --version
containerd github.com/containerd/containerd v1.6.0-rc.1 ad771115b82a70cfd8018d72ae489c707e63de16.m

./bin/containerd-shim-runc-v1 -v
./bin/containerd-shim-runc-v1:
Version:  v1.6.0-rc.1
Revision: ad771115b82a70cfd8018d72ae489c707e63de16.m
Go version: go1.17.2

./bin/containerd-shim-runc-v2 -v
./bin/containerd-shim-runc-v2:
Version:  v1.6.0-rc.1
Revision: ad771115b82a70cfd8018d72ae489c707e63de16.m
Go version: go1.17.2

Describe the results you received and expected

No .m in the commit

What version of containerd are you using?

containerd github.com/containerd/containerd v1.6.0-rc.1 ad77111.m

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions