Open PureTryOut opened 1 year ago
I think this may be attributed to managing versions across three locations: Docker tags, GitHub tags and the IRIS_VERSION
file.
I've made a new release which should test this theory. Can you please check the latest version is matching up at 3.69.2?
Close enough, it reports 3.69.0 now :see_no_evil:
INFO 2023-10-24 07:23:16,477 [2:IrisFrontend-12] mopidy_iris.core
Starting Iris 3.69.0
Podman says the container is running 3.69.2 as expected though.
Can you please include your docker-compose.yml
file? What image version are you specifying?
I have this:
mopidy:
container_name: mopidy
image: jaedb/iris:3.69
and it is successfully starting as expected:
and reporting in the UI as expected:
I don't use Docker compose. I use Ansible instead but it achieves the same result.
containers.podman.podman_container:
name: "mopidy"
image: "docker.io/jaedb/iris:3.69.2"
state: "started"
restart_policy: "always"
volumes:
- "/etc/mopidy/mopidy.conf:/var/lib/mopidy/.config/mopidy/mopidy.conf:ro"
- "/var/lib/mopidy:/var/lib/mopidy"
- "/run/snapserver:/run/snapserver"
- "/etc/asound.conf:/etc/asound.conf:ro"
env:
PIP_PACKAGES: "yt-dlp Mopidy-Youtube Mopidy-Soundcloud"
publish:
- "6600:6600"
- "6680:6680"
As you can see I'm even specifying the patch version, still Iris web UI says it's running 3.69.0...
Iris version
Well, that's the question...
Operating system(s) affected
Browser(s) affected
What happened?
My server is running version 3.68.0 of the Docker image, but the web UI is reporting it's still running 3.67.0.
Logs