-
Notifications
You must be signed in to change notification settings - Fork 654
Provided detailed commands to backup and upgrade Rustdesk #536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I expanded on the commands to provide more detailed instructions on how to perform a backup of Rustdesk as well as bringing down the docker containers, removing the containers, removing the images, pruning any unused images, and finally pulling and bringing back up a fresh image of Rustdesk docker container.
…iners Changed command to use less aggressive "stop" for bringing down containers
juanchomang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changed:
docker kill
for a more gentle:
docker stop
|
Coud you confirm if below better If Your commands work, but it is not a docker compose way. :( |
|
Sure, that works for upgrading but it does not clean up unused images. |
Will work? |
|
Yes, that would work very well. |
|
Interesting, the |
|
I will try at the next version upgrade as it is not possible to replicate the environment now that I have upgraded... I even tried to pull an older image but the tag doesn't match so it won't overwrite... |
|
I will try this: docker compose down |
|
Thanks, great. |
docker compose pull
docker compose up -dThis will reduce downtime. The first command pulls the new image; the second command switches to the new image and recreates the container without having to wait for the pull process (though both RustDesk OSS and Pro server images are small). After Docker switches to the new image, the old one becomes a "dangling image" (unused). Users should remove it themselves if needed. We should not suggest users run this command, as they may be unfamiliar with Docker and risk causing data loss. We shouldn't have to take this responsibility. docker image prune -f |
I expanded on the commands to provide more detailed instructions on how to perform a backup of Rustdesk as well as bringing down the docker containers, removing the containers, removing the images, pruning any unused images, and finally pulling and bringing back up a fresh image of Rustdesk docker container.