#Can't run medusa cli in docker container

48 messages · Page 1 of 1 (latest)

pulsar ridge
#

Hey guys i build a docker container and trying to run medusa in production mode. While trying to use the medusa cli in the docker container i get the message
"Test server running at http://127.0.0.1:3000/
Stopping test server..."

Did anyone of you experience this too?

proper hemlock
#

I am interested in this thread as I face memory issues with my medusa installation locally 👍

pulsar ridge
#

are u using redis?

#

I somewhere read that memory issues can occur when you are running on the fake redis

proper hemlock
#

Basically I use medusa with the fake one, but I start it sometimes

pulsar ridge
#

You could try to use redis, i don't know how they implemented the fake one, it's probably not as efficient as the real one.

proper hemlock
#

Absolutely

pulsar ridge
#

version: "3.8"
services:
redis:
image: redis:7.0.11-alpine
container_name: redis
expose:
- "6379:6379"
command: redis-server --requirepass redis-password
volumes:
- redis:/data
volumes:
redis:
driver: local

#

here a compose you could use

#

im using this right now to test out the solution

#

lol there is an error in expose

#

i need to refactor it to ports

proper hemlock
#

Let's try to keep your thread up instead of talking about memory, but do you think it's linked ?

pulsar ridge
#

I actually don't know im trying to debug it right now but debug logs are sparse 😄

#

it shouldnt be the case the port should be exposed

#

and i select it over the internal docker network by the service name

#

especially because logs show it is connected

proper hemlock
pulsar ridge
#

yeah

#

i set node_env to production

#

because i have to test the deployment locally for prod

#

i want to deploy it on digital ocean

#

and it allready ran, but since adding the fileservices the medusa cli is not working anymore so i cant create an admin account to test the solution

#

i also allready set the all the necessary flags for prod im just wondering what i did wrong

proper hemlock
#

I am not an expert of Docker but have you noticed that the actual version of Medusa is v1.8 and that the admin has become a plugin

pulsar ridge
#

yeah you have the admin dashboard as a plugin now

#

i will probably have to fork the admin ui

#

because i want to give my customers the possibilty to brand it

#

and multi language is still an issue

#

just a screenshot to show my problem

#

lol there is asmongold in the background XD

pulsar ridge
#

man the funny part is that medusa is actually returning its verions string

proper hemlock
#

This is the version of medusa-cli, right ? But actually it's v1.3.9

pulsar ridge
#

omg

#

my eyes are bleeding

#

you are a real bro my dude

#

i used medusa-cli not @pulsar islejs/medusa-cli

#

fml

#

ima try it out

#

maybe my brain needs breaks when im doing 60-80 hours work weeks

#

it works!

proper hemlock
#

Niceee 👏
Thank you, I try to understand and point out to the right resource/doc
medusajs has a sort of naming convention that uses medusa-something like for example medusa-plugin-something
After 80 hours of work I understand that you can be confused

pulsar ridge
#

thanks a lot good sir 😄

proper hemlock
pulsar ridge
#

ah sorry im on vacation now