Docker container not starting up after replacing the r3 file

Hemanth_L

Hi,
I have cloned the latest application files from the github and I have a docker container which is running on version R3.11.10.6056, and I made a quite small changes in the application and tried to build an r3 binary file using the below commands,

            $env:GOOS="linux"
	$env:GOARCH="amd64"
	go build -ldflags "-X main.appVersion=3.11.10.6056"

and tried to replace the r3 binary file in the docker container but i get an error, saying

E: 11:02:34 failed automatic upgrade of database, DB version '3.11' not recognized, platform update required

Shutting down...

and also is there any way to get to know the complete version after each update/release

gabriel

Hemanth_L and also is there any way to get to know the complete version after each update/release

I do not understand what you mean by this. Do you mean a full change history of every release? This you can find here:
https://rei3.de/en/docs/changelog

gabriel

The error occurs if the binary found a version mismatch between the database version it found when connecting to the database (3.11), and the version of the binary itself.

Could you please run r3 directly via CLI to check what the binary thinks its version is? If you just run r3 directly, a help page is shown which includes the version number.

Hemanth_L

gabriel Thanks for the suggestion! Running r3 directly helped me spot the version mismatch—the binary was on a different version. I rebuilt it with the correct version, and everything is working now. Appreciate the help!

Hemanth_L

gabriel Thanks for sharing the changelog link!

What I’m looking for is slightly different — not just the release version like "3.11.10", but the complete build version (for example, "3.11.10.6056").

From what I’ve seen, the changelog only lists versions up to "3.11.10", and the last four digits seem to only be visible when running the app (e.g., via Docker).

Is there any place where the full build/version number is documented, or is checking it from the running container the only way?

gabriel

Hemanth_L
This does not exist because we do not track changes by build number. Build numbers serve to know how old a specific development build is. Every public release has a new minor/patch version number, such as 3.9.1 or 3.11.10.

If you build your own r3 versions, you need to have a higher build number so that apps will install - for this you need to know the build number. To find the build number, you can run the binary of any public release or check in the admin panel in any running r3 instance (Admin -> System -> General).