I’m a bit confused with updating chirpstack on the docker compose project.
In my case, I only need the chirpstack service (no “gateway-bridge” or “basic-station”) from the docker project.
I found the following post to this topic:
So is it correct that I only need to update the chirpstack version in the docker-compose.yml file (and do potential manual migrations like from version “4.6.0” to “4.7.0”) or are there other steps involved?
E.g. I would change chirpstack/chirpstack:4 to chirpstack/chirpstack:4.10.2 in the yml file.
What I also don’t get is, when I pull a new docker project, the current chirpstack version in the yml file is “4” (as mentioned above) but in the logs the version is “4.6.0”.
Yes this is correct, updating the number in the docker compose is all thats necessary, then doing
docker-compose pull chirpstack
docker-compose up -d
or similar.
This is strange, 4 should just pull the newest version 4.10.2. Maybe this was purposeful though as there were some changes in 4.7 that would cause your system to fail if automatically updated (you need to run migration commands). If you want it to auto update (on restart) you could try just:
image: chirpstack/chirpstack:latest
This is what I’ve been using for a while and it works as expected.
Thats also what I thought, but I just couldn’t find a description for that.
For that reason I wouldn’t use ‘latest’. If there would be a future version with manual migrations.
