12 Replies
Did you follow the instruction in the release note?
yes i did
depends on
and the new container
Can you bring everything down then up again, then monitor the log to see if anything go wrong
023-03-20T18:44:01.489586440Z Error: Config validation error: "TYPESENSE_API_KEY" is required
2023-03-20T18:44:01.489587735Z at Function.forRoot (/usr/src/app/node_modules/@nestjs/config/dist/config.module.js:75:23)
2023-03-20T18:44:01.489588970Z at Object.<anonymous> (/usr/src/app/dist/apps/immich/apps/immich/src/app.module.js:39:35)
2023-03-20T18:44:01.489590436Z at Module._compile (node:internal/modules/cjs/loader:1105:14)
2023-03-20T18:44:01.489591572Z at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
2023-03-20T18:44:01.489592707Z at Module.load (node:internal/modules/cjs/loader:981:32)
2023-03-20T18:44:01.489593823Z at Function.Module._load (node:internal/modules/cjs/loader:822:12)
2023-03-20T18:44:01.489594986Z at Module.require (node:internal/modules/cjs/loader:1005:19)
2023-03-20T18:44:01.489596268Z at require (node:internal/modules/cjs/helpers:102:18)
2023-03-20T18:44:01.489597387Z at Object.<anonymous> (/usr/src/app/dist/apps/immich/apps/immich/src/main.js:12:22)
2023-03-20T18:44:01.489598596Z at Module._compile (node:internal/modules/cjs/loader:1105:14)
got this on error server
seems not finding typesense_api_key but is set
Check for typoes then
unale to find it
:/
going dinner check again later
solved.
a sort of problem with portainer
@spupuz | love I'm having this issue, too. What was your fix?
I used the notepad++ compare plugin to compare my compose file with the official one, so I know there's no typo's. I guess this one requires more google fu
You can share your docker-compose so we can help
and also the .env file
Oh, I think I know what the issue, that's on me
Yup. Okay, I was trying to put the string in the compose file instead of creating an ENV variable for it because I'm a docker newb, but got it now.
Was that you on the release discussion? 😄
@spupuz | love @Stencil would you mind sharing some insight on how you were able to get this resolved? i am having the same issues but could not find anything on the stack file or the env variables that may cause the typesense container not to start. tia
@ayosnato pay attention that ney typesense api is passes to all the containers (server microservices and typesense)