Closed lyz-code closed 3 years ago
I'm gonna wager a guess that the app is displaying incorrect info.
Our builder passes the version as a docker arg and that arg is used to pull the grocy version from upstream repo: https://github.com/linuxserver/docker-grocy/blob/master/Dockerfile#L32
We are indeed pulling and installing the said version.
You can see here in the build log that the GROCY_RELEASE
arg is clearly passed as v2.6.2
: https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-grocy/detail/master/163/pipeline/131#step-142-log-1
Should now be fixed, there is also a new branch from now on for releases, see https://github.com/grocy/grocy/issues/698#issuecomment-609072280.
@berrnd thanks for the heads up. We'll pull from the new location
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
Docker image with tag
latest
orv2.6.2-ls53
should contain version 2.6.2 of the application.Current Behavior
When doing
docker pull
the image starts version 2.6.1, and the digest doesn't match the one in dockerhub.Steps to Reproduce
docker pull linuxserver/grocy:latest
ordocker pull linuxserver/grocy:v2.6.2-ls53
.admin/admin
About Grocy: Version 2.6.1
Environment
OS: Debian Buster CPU architecture: x86_64
How docker service was installed: with the docker guide.
Command used to create docker container (run/create/compose/screenshot)
See above