Replies: 1 comment
-
|
Thanks for the question! This is actually a common point of confusion. The issue is that the docker-compose.yml was using build: instead of referencing pre-built images. When you ran docker compose pull, nothing happened because there was no image reference to pull. I've just updated the compose file to use pre-built images by default. Going forward, upgrading will be as simple as: Or use the included update script: Linux/Mac: ./update.sh The pre-built images are published to: GitHub Container Registry: ghcr.io/itz4blitz/logarr-backend and ghcr.io/itz4blitz/logarr-frontend To pin to a specific version (recommended for production), set |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I don't want to start an Issue for this, more of just a question. What is the best way to upgrade when you release a new version? I tried just doing a
docker compose down, followed by pulling the new frontend/backend images, thendocker compose up -dagain, but that doesn't seem to be enough as it indicated I was still on 0.4.5 after doing that earlier today. I had to pretty much wipe out the local folder I had created with the installations git clone command, wipe the old images from my Docker, and re-install, but I imagine there is a cleaner way of doing this.Beta Was this translation helpful? Give feedback.
All reactions