Container started
panic: version: Numeric PreRelease version must not contain leading zeroes "093655760"
goroutine 1 [running]:
storj.io/common/version.getInfoFromBuildTags()
/go/pkg/mod/storj.io/common@v0.0.0-20251022143549-19bf6a9f274a/version/version.go:343 +0x2cb
storj.io/common/version.init.0()
/go/pkg/mod/storj.io/common@v0.0.0-20251022143549-19bf6a9f274a/version/info.go:15 +0x25
Container stopped
Will the multinode container (storjlabs/multinode:latest) ever work again?
Yes, with the next release where the commit hash doesn’t start with zero. It’s already fixed to me.
Unable to find image 'storjlabs/multinode:latest' locally
latest: Pulling from storjlabs/multinode
b338562f40a7: Already exists
d6352344dc72: Pull complete
1dd735ea721e: Pull complete
dec151b6a8f8: Pull complete
e0f0d8b1cbb8: Pull complete
Digest: sha256:d42525cafee5571947ad9b82feb87fab42f0fd3d8b55e8a3b8cd55b619335ba2
Status: Downloaded newer image for storjlabs/multinode:latest
2025-11-10T15:49:52Z INFO Anonymized tracing enabled
2025-11-10T15:49:52Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2025-11-10T15:49:52Z INFO Anonymized tracing enabled
2025-11-10T15:49:52Z INFO db Database Created {"version": 0}
^C2025-11-10T15:50:11Z INFO Got a signal from the OS: "interrupt"
But it shouldn’t happen again. Will check how can it be permanently fixed…