From 8ebcbabfcab10f585fe6cab99e7eb3c005ad32a4 Mon Sep 17 00:00:00 2001 From: juanchomang Date: Fri, 30 May 2025 21:39:47 -0700 Subject: [PATCH 1/2] Provided detailed commands to backup and upgrade Rustdesk 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. --- content/self-host/rustdesk-server-pro/faq/_index.en.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/self-host/rustdesk-server-pro/faq/_index.en.md b/content/self-host/rustdesk-server-pro/faq/_index.en.md index e05df848..9de70915 100644 --- a/content/self-host/rustdesk-server-pro/faq/_index.en.md +++ b/content/self-host/rustdesk-server-pro/faq/_index.en.md @@ -34,7 +34,12 @@ You'd better back up data files (sqlite3 files etc.) first, https://github.com/r 3. Follow the prompts as they guide you through the upgrade. #### Docker Compose ``` -docker compose up -d --build --pull always +tar -czvf "RustdeskDB$(date +'%Y%m%d%H%M%S').tar.gz" /path/to/your/data +docker kill hbbr hbbs # Stop the running containers +docker rm hbbr hbbs # Remove the stopped containers +docker rmi rustdesk/rustdesk-server-pro # Remove the current RustDesk image +docker image prune -f # Clean up any unused, untagged images (this will clear out _every_ unused or untagged docker image on the system, without asking!) +docker compose up -d --build --pull always # Pull and rebuild the latest image ``` But this depends on your docker version, for more discussion, check [this](https://stackoverflow.com/questions/37685581/how-to-get-docker-compose-to-use-the-latest-image-from-repository). #### Docker From efb1f104dad717f03d846f6ab9c3e35c3e8ab378 Mon Sep 17 00:00:00 2001 From: juanchomang Date: Fri, 30 May 2025 21:44:40 -0700 Subject: [PATCH 2/2] Changed command to use less aggressive "stop" for bringing down containers Changed command to use less aggressive "stop" for bringing down containers --- content/self-host/rustdesk-server-pro/faq/_index.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/self-host/rustdesk-server-pro/faq/_index.en.md b/content/self-host/rustdesk-server-pro/faq/_index.en.md index 9de70915..4a6b8527 100644 --- a/content/self-host/rustdesk-server-pro/faq/_index.en.md +++ b/content/self-host/rustdesk-server-pro/faq/_index.en.md @@ -35,7 +35,7 @@ You'd better back up data files (sqlite3 files etc.) first, https://github.com/r #### Docker Compose ``` tar -czvf "RustdeskDB$(date +'%Y%m%d%H%M%S').tar.gz" /path/to/your/data -docker kill hbbr hbbs # Stop the running containers +docker stop hbbr hbbs # Stop the running containers docker rm hbbr hbbs # Remove the stopped containers docker rmi rustdesk/rustdesk-server-pro # Remove the current RustDesk image docker image prune -f # Clean up any unused, untagged images (this will clear out _every_ unused or untagged docker image on the system, without asking!)