0.11.5 :[Jul 30]

Discord-Discussions
1

:raising_hand_man: wkw asked

this is a known bug before 0.11.1

2

:raising_hand_man: afriadi replied

ah ok, thanks for the response wkw@discord , is there any way to resolve this? or the only way is to delete and start new?

3

:raising_hand_man: wkw replied

r u importing to the same instance?

4

:raising_hand_man: afriadi replied

basically we are using docker image, and we update the docker image to latest version available

5

:raising_hand_man: afriadi replied

and then it is broken, although previously we are using 0.11.2 and it working just fine

6

:raising_hand_man: afriadi replied

we are using kubernetes, so when our deployment image changes, it will start new pod

7

:raising_hand_man: afriadi replied

but it won’t start due to error that I’ve posted

8

:raising_hand_man: wkw replied

it s kinda not my case then. i was using docker with 2 different instances. i suggest u include these info in your comment as well Bug: failed to import meta data · Issue #343 · nocodb/nocodb · GitHub

9

:man_technologist: pranavxc replied

Can you mount any volume?

10

:man_technologist: pranavxc replied

if possible please share more details about meta DB, which database are you using as metadatabase? (default one is file-based SQLite - noco.db)

11

:raising_hand_man: afriadi replied

haven’t try this

12

:man_technologist: pranavxc replied

you can mount the volume at /usr/app/data/ , which will help to persist data(attachment files, noco.db, etc… )

13

:raising_hand_man: afriadi replied

we are using rds mariadb

14

:raising_hand_man: afriadi replied

and we are using kubernetes to deploy the nocodb instance

15

:man_technologist: pranavxc replied

Looks fine, hope it will use the same database even after upgrading

16

:raising_hand_man: afriadi replied

noted, I’ll try this later, but right now we could not use the nocodb, even after revert back to 0.11.2

17

:raising_hand_man: afriadi replied

do we need to reset the databased used, delete and let nocodb recreate it

18

:raising_hand_man: afriadi replied

or there are workarounds for this issue

19

:man_technologist: pranavxc replied

that error is related to decrypting project config… if you using the same database then it won’t happen usually(since the keys will be the same)

20

:raising_hand_man: afriadi replied

ic, we are using the same db from the start, when upgrading to 0.11.2 it working fine, after it is upgraded to 0.11.5 it shows error, and when we revert back to 0.11.2 it still shows error