Metabase reset after heap update

Get Help
1

I followed steps mentioned in documentation to increase heap memory.

more specifically, I ran following commands:

sudo docker stop metabase

sudo docker run --rm -v metabase-data:/volume -v $(pwd):/backup busybox tar czf /backup/metabase-data-backup.tar.gz -C /volume .

sudo docker rm metabase

sudo docker run -d --name metabase --memory=2500m --memory-swap=3000m -e JAVA_OPTS="-Xms512m -Xmx1700m" -v metabase-data:/metabase-data -p 3000:3000 metabase/metabase

sudo docker run --rm -v metabase-data:/volume busybox ls /volume

sudo docker start metabase

This resulted in starting metabase from beginning configurations.
Is there some way to recover previous configurations? Which step was unnecessary? which step has caused the problem? Is it possible to update heap without running metabase again?

2

Please run Metabase with an application database, otherwise you’ll keep loosing everything since your volume mounts are wrong

3

Thank you. Please elaborate or share the link that I can use.
Corrected the reference link I had used in original post.

4

I see db backup in host

sudo du -h /var/lib/docker/volumes/metabase-data/_data/metabase.db.mv.db
711M /var/lib/docker/volumes/metabase-data/_data/metabase.db.mv.db

can I restore that to the docker container?
du -h /metabase.db/*
1.3M /metabase.db/metabase.db.mv.db
212K /metabase.db/metabase.db.trace.db

5

Thank you for your help.

I have resolved it with

sudo docker run -d \
--name metabase \
--memory=2500m --memory-swap=3000m \
-e JAVA_OPTS="-Xms512m -Xmx1700m" \
-e MB_DB_FILE=/metabase-data/metabase.db.mv.db \
-v metabase-data:/metabase-data \
-p 3000:3000 \
metabase/metabase

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.