How to upgrade the running memos container without losing data?

[erbanku]

Thanks for making this awesome software. After installing & running memos (Sorry, I am new to docker) how can I update the container?

I am able to update the image, but unable to apply this update to the running memos container. Can you help me out? Thanks.

[Zeng1998]

There are too many ways, it's up to you.

For me, I like to use raw docker commands.

1. backup your database file (~/.memos/memos_prod.db), it's optional.
2. stop the running container.
3. remove the container.
4. remove the image.
5. get the latest image and run a new container. (https://github.com/usememos/memos#docker-run)

[erbanku]

Success, awesome! Thanks.

[AssistantLiu]

vim updatememos.sh
chmod 777 updatememos.sh

# Onekey update memos to latest

# list running container
docker ps

# list all exist images
docker images

# backup db
cp ~/.memos/memos_prod.db .

# rm container
docker rm -f memos

# rm image
docker rmi neosmemo/memos:latest

# update to latest
docker run -d --name memos -p 5230:5230 -v ~/.memos/:/var/opt/memos neosmemo/memos:latest

[erbanku]

@AssistantLiu Thanks a lot.

[erbanku]

Changed a bit.

# This script is used to update memos to the latest version.

# backup db with timestamp
cp ~/.memos/memos_prod.db ~/Backup/memos-db-backup/$(date +%Y%m%d%H%M%S).memos_prod.db

# rm container
docker rm -f memos
# rm image
docker rmi neosmemo/memos:latest

# Update to latest
docker run -d --name memos -p 5230:5230 -v ~/.memos/:/var/opt/memos neosmemo/memos:latest
# Get Docker memo container id and save this to variable memos_id
memos_id=$(docker ps | grep memos | awk '{print $1}')


# Enable docker service to run on startup
sudo systemctl enable docker.service
# Setup memos docker container to run on startup
docker update --restart=always $memos_id

[louzc]

If you are the admin of the server, you can also use watchtower

[erbanku]

I will try it out. Thanks. 😉

[JeauLiang]

These codes are backup the database and recreate the container, how can I restore the database after recreate the container?

[woshichenghaibo]

These codes are backup the database and recreate the container, how can I restore the database after recreate the container?

同问

[hossain-khan]

📝 UPDATE

I was able to restore all memos to new docker container instance. Instead of just coping the db file memos_prod.db you have to copy all 3 files. Then it works perfectly, including admin account. ✅

Now, my /portainer/Files/AppData/Config/memo-notes/ contains all 3 files before creating the container.

• memos_prod.db
• memos_prod.db-shm
• memos_prod.db-wal

---

I have copied the memos_prod.db file from one container to another to replicate the whole instance. It didn't work.

I got the following error

---
Server profile
version: 0.22.1
data: /var/opt/memos
dsn: /var/opt/memos/memos_prod.db
addr: 
port: 5230
mode: prod
driver: sqlite
---
2024/06/07 02:46:19 ERROR failed to migrate database !BADKEY="SQL logic error: no such table: migration_history (1)\nfailed to find migration history\ngithub.com/usememos/memos/store/db/sqlite.(*DB).Migrate\n\t/backend-build/store/db/sqlite/migrator.go:49\nmain.init.func1\n\t/backend-build/bin/memos/main.go:52\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:987\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1115\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1039\nmain.Execute\n\t/backend-build/bin/memos/main.go:100\nmain.main\n\t/backend-build/bin/memos/main.go:183\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:271\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_arm64.s:1222"

Used following compose command

version: "3.0"
services:
  memos:
    image: neosmemo/memos:stable
    container_name: memos
    volumes:
      - /portainer/Files/AppData/Config/memo-notes/:/var/opt/memos
    ports:
      - 5230:5230