Closed hilyin closed 3 years ago
Hello this log isn't really helpful as you don't share steps to reproduce. From what I am seeing you just need to yarn add the mysql package. I'm going to close this util you update the description ;)
steps to repro:
docker-compose up
I am supposed to yarn or npm add inside a container?
or outside on the host system? which would defeat the purpose of using docker no?
docker compose up of what ? what is your setup and config ?
the mysql docker-compose.yml
config? this is first run.
Are you running an existing project or waiting for it to generate ?
brand new project, i am expecting strapi to start a fresh install w/ mysql service attached. but it fails on that yarn/npm package inside the container.
How did you make that install ? by default it is using sqlite.
How did you make that install ? by default it is using sqlite.
Sir, I am using your docker-compose.yml provided in the repo.
examples/mysql/docker-compose.yml
I literally just run docker-compose up
with that file, expecting it to handle installing node modules itself within the container it requires them. I am just trying to setup a brand new install with your provided docker-compose.yml
.
I gotta say, I am really frustrated with the response I got from this team.
Please understand your file examples/mysql/docker-compose.yml
in your repo is broken. It needs to be repaired so when you start a fresh instance it actually installs and sets up properly. I am beyond frustrated with trying to set this up.
The fact that this ticket was immediately closed shows how supportive your "support" team is.
Hello @hilyin until your last comment I didn't know which docker-compose file you were using.
Now, I just tried running the ./examples/mysql/docker-compose.yml
configuration whithout bugs so I will need a bit more details to help you.
docker-compose logs strapi
, you should see a log Using strapi x.y.z
can you give me that version ?./app
folder. If so can you check that the package.json as a mysql
dependency ?To help our community the best we triage the tickets but still answer to them. As you can see you didn't have to wait for any answer until the weekend (yes maintainers do get to have a life too ;))
A kind reminder that you are using an open source project and not paying for a support service. Rest assured we do our best to help out everyone in our community in a timely fashion. :) Finally I will point you to our code of conduct here so you are aware of the expected bahaviors on our repositories.
Have a great day !
it was in the subject line of this issue the entire time. i’ve moved onto an alternate solution. good day.
error: