#Medusa backend in docker: error starting server

5 messages · Page 1 of 1 (latest)

pearl crow
#

Hi people,

I'm having a bit of trouble hosting my backend in docker. A lot of this trouble is due to my project structure. I've got a pnpm monorepo (turbo). That means e.g. that I don't have a specific package-lock file for the backend only.

I've chewed threw a ton of complications and errors, but now I'm facing something which I don't quite know how to solve. I don't really get an error, just a stacktrace: https://gist.github.com/ericwaetke/add5ce2f55c2019ffa28e5b79d1b6a7c

Here is my dockerfile and medusa-config
https://gist.github.com/ericwaetke/c5a0b31ac5a8b5fc20e6e249f0fdd35c

Maybe one of you has an Idea what the cause of this might be?

Thanks!

Gist

Stacktrace. GitHub Gist: instantly share code, notes, and snippets.

Gist

GitHub Gist: instantly share code, notes, and snippets.

#

Okay I think it was just my stupidness. Somehow the JWT_SECRET and COOKIE_SECRET managed to disappear from my .env, so I didnt set them in the production env. On fly.io, I only got the stacktrace, when I ran the Dockerimage locally however, I got an error that those things aren't set.

subtle slate
#

What are you using for medusa in docker? Every repo I've come across is old and not working

pearl crow
#

What do you mean with what I am using?
What I use to host the Container?

I basically just spin up a container and run the start command, which runs the migrations and then starts medusa

subtle slate
#

I meant to say what repo are you using or did you create your own?