Closed jaycoolslm closed 1 month ago
Hi! Thanks for reporting this. I used to run into the same problem all the time before. We'll try to test the dev version when we get some time.
Adding platform: linux/amd64
made it work on my side.
I have added it on every service.
ex:
services:
server:
platform: linux/amd64
build:
context: ./server
dockerfile: ../config/development/Dockerfile.server
....
I am on MacOS v13, and use https://orbstack.dev/ to run my docker set-up.
Thanks @lebaudantoine will try this out... but off experience I imagine this is the fix... usually is when running docker on ARM chips XD so much for containerisation being operable on all OS haha
Yup this worked (ish)... its actually only needed for the client container though. Server container is okay - client container has deps on node-sass
Where is the problem occurring?
I'm not sure
What browsers are you seeing the problem on?
Other
Current behaviour
I am using a M2 macbook pro and running
docker compose -f docker-compose-dev.yml up -d
on my machine. Am then met with this error. Looks like something to do withnode-sass
distutils
looks like same error as here https://github.com/plankanban/planka/issues/818
Desired behaviour
In this situation I expect that the the docker containers spin up first time
Steps to reproduce
cloned repo,
docker compose -f docker-compose-dev.yml up -d
Other information
No response