- Node.js version: v14.16.0
- NPM version: 6.14.11
- Strapi version: 4.0.2
- Database: postgres
- Operating system: official strapi/base image
How does your docker file look?
Hey @Eventyret ,
Here are content of my Dockerfile
# pull official base image FROM strapi/base # set working directory # We select this directory because webstorm requires this path for remote debugging setup. WORKDIR /opt/project # Docker images are created layer by layer, so when we are just coping package.json files it would not get build everytime # we do any update on the files apart from package.json. It only gets rebuild when we add a new package or we change something on the package.json file. # We generally create the package required layer first and then load the code file, so that the build get triggered only when we do any update on requirements. # If we copy the whole codebase then the image will have to rebuild always since the layer on which we are loading the files updates on every code update. COPY ./package.json ./yarn.lock ./ RUN yarn install COPY . .
Content of my docker compose file
version: '3' services: dummy-app: build: dockerfile: ./Dockerfile.local context: ./dummy-app command: yarn develop volumes: - ./dummy-app:/opt/project - /opt/project/node_modules/ ports: - '1337:1337' env_file: - ./.prod.env
Just an observation. And I don’t think it matters.
But strapi base is a v3 project and your using v4
Would that not also cause issues