Description
Every release since the release v20.10.43 of balena engine, running --version or version returns dev with build at HEAD
Steps to reproduce the issue:
- Download version v20.10.19+
- Run balena-engine version or balena-engine -v
- Read output
Describe the results you received:
balena-engine -v:
balenaEngine version dev, build HEAD
balena-engine version:
Client:
Version: dev
API version: 1.41
Go version: go1.17.11
Git commit: HEAD
Built: Mon Feb 5 13:11:19 2024
OS/Arch: linux/arm
Context: default
Experimental: true
Server:
Engine:
Version: dev
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: HEAD
Built: Mon Feb 5 13:11:19 2024
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.6.6+unknown
GitCommit:
runc:
Version: unknown
GitCommit:
version is dev with build at HEAD
Describe the results you expected:
version v20.10.19 with correct build hash
Additional information you deem important (e.g. issue happens only occasionally):
Output of balena-engine version:
dev
Client:
Version: dev
API version: 1.41
Go version: go1.17.11
Git commit: HEAD
Built: Mon Feb 5 13:11:19 2024
OS/Arch: linux/arm
Context: default
Experimental: true
Server:
Engine:
Version: dev
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: HEAD
Built: Mon Feb 5 13:11:19 2024
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.6.6+unknown
GitCommit:
runc:
Version: unknown
GitCommit:
Output of balena-engine info:
Client:
Context: default
Debug Mode: false
Server:
Containers: 6
Running: 0
Paused: 0
Stopped: 6
Images: 1
Server Version: dev
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host null
Log: journald json-file local
Swarm:
NodeID:
Is Manager: false
Node Address:
Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: balena-engine-init
containerd version:
runc version:
init version: N/A
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.103-v7l+
Operating System: Raspbian GNU/Linux 10 (buster)
OSType: linux
Architecture: armv7l
CPUs: 4
Total Memory: 971.2MiB
Name: xxxx
ID: xxxx
Docker Root Dir: /var/lib/balena-engine
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory TCP limit support
WARNING: No oom kill disable support
Additional environment details (device type, OS, etc.):
CM4 running Buster
Description
Every release since the release v20.10.43 of balena engine, running --version or version returns dev with build at HEAD
Steps to reproduce the issue:
Describe the results you received:
balena-engine -v:balenaEngine version dev, build HEADbalena-engine version:version is dev with build at HEAD
Describe the results you expected:
version v20.10.19 with correct build hash
Additional information you deem important (e.g. issue happens only occasionally):
Output of
balena-engine version:dev
Output of
balena-engine info:Additional environment details (device type, OS, etc.):
CM4 running Buster