Replies: 1 comment 2 replies
-
Hello @sticky99 If you have installed it from our original YAMLs and you are on the same base version of the repository (4.3) you can update the repository, change to the most current tag, and start the stack again, since the volumes that will be used are the same. cd single-node
docker-compose down
cd ..
git pull
git checkout v4.3.9
cd single-node
docker-compose up -d If you have made any changes to the directories or have your own YAML to deploy, modifying the version of each image in the docker-compose.yml is enough. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I installed the Manager, Dashboard, and Indexer as a single node (v4.3.5) a few months back, and installed the same version agent on a few devices on my home network. Now the agents are updating (semi-automatically) but the docker containers are not. I generally use Watchtower for container updates, but from debugs I can see it just checks if there's a more recent 4.3.5 version available, rather than looking for a more recent version number.
So is there a recommended update procedure, or is just to do a "docker rm" and "docker pull" and everything should work as before?
Beta Was this translation helpful? Give feedback.
All reactions