Invalid response error with socket time out while building Dockerfile with docker-compose.yml - docker-compose

Question

I'm now trying to make a monorepo project.
My directory structure looks like this:
word_mono
|- apps
|- shadowing_list
|- backend
|- (Nest project here, made up with nest command)
|- Dockerfile
|- frontend
|- shadowing_trend
|- shared
|- database
|- Dockerfile
|- schema.prisma
|- .env
|- docker-compose.yml
On current stage, I'm now implementing shadowing_list's backend with postgresql, prisma, and nest js with docker.
So my docker-compose.yml file is like this
version: "3.8"
services:
shadowing-list-backend:
container_name: shadowing-list-backend
restart: on-failure:10
ports:
- "8000:8000"
build:
context: ./
dockerfile: ./shadowing_list/backend/Dockerfile
volumes:
- /usr/src/app/node_modules
- ./shadowing_list/backend/:/usr/src/app
env_file:
- .env
depends_on:
- prisma
- db
prisma:
image: prismagraphql/prisma:1.34
container_name: prisma
restart: always
ports:
- "4466:4466"
environment:
PRISMA_CONFIG: |
port: 4466
databases:
default:
connector: postgres
host: db
port: 5432
user: ${POSTGRES_USER}
password: ${POSTGRES_PASSWORD}
database: ${POSTGRES_DB}
migrations: true
env_file:
- .env
links:
- db
db:
build:
context: ./shared/database
container_name: postgres
env_file:
- .env
ports:
- "5432:5432"
volumes:
- ./shared/database/db-data:/var/lib/postgresql/data
volumes:
db-data:
the Dockerfile in shadowing_list/backend:
# Build context /apps/
FROM node:16
WORKDIR /usr/src/app
# Install prisma
RUN npm install -g prisma
# Copy package.json
COPY shadowing_list/backend/package.json ./
RUN npm install
# Cache all after package installed
COPY shadowing_list/backend ./
# Use schema.prisma file in shared folder
COPY shared/database/schema.prisma .
RUN prisma generate
EXPOSE 8000
CMD ["npm", "start"]
the package.json file of shadowing_list/backend:
{
"name": "backend",
"version": "0.0.1",
"description": "",
"author": "",
"private": true,
"license": "UNLICENSED",
"scripts": {
"prebuild": "rimraf dist",
"build": "nest build",
"format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",
"start": "nest start",
"start:dev": "nest start --watch",
"start:debug": "nest start --debug --watch",
"start:prod": "node dist/main",
"lint": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix",
"test": "jest",
"test:watch": "jest --watch",
"test:cov": "jest --coverage",
"test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand",
"test:e2e": "jest --config ./test/jest-e2e.json"
},
"dependencies": {
"#nestjs/common": "^9.0.0",
"#nestjs/core": "^9.0.0",
"#nestjs/graphql": "^10.1.7",
"#nestjs/platform-express": "^9.0.0",
"#prisma/client": "^4.9.0",
"dotenv": "^16.0.3",
"reflect-metadata": "^0.1.13",
"rimraf": "^3.0.2",
"rxjs": "^7.2.0"
},
"devDependencies": {
"#nestjs/cli": "^9.0.0",
"#nestjs/schematics": "^9.0.0",
"#nestjs/testing": "^9.0.0",
"#types/express": "^4.17.13",
"#types/jest": "28.1.8",
"#types/node": "^16.0.0",
"#types/supertest": "^2.0.11",
"#typescript-eslint/eslint-plugin": "^5.0.0",
"#typescript-eslint/parser": "^5.0.0",
"eslint": "^8.0.1",
"eslint-config-prettier": "^8.3.0",
"eslint-plugin-prettier": "^4.0.0",
"jest": "28.1.3",
"prettier": "^2.3.2",
"source-map-support": "^0.5.20",
"supertest": "^6.1.3",
"ts-jest": "28.0.8",
"ts-loader": "^9.2.3",
"ts-node": "^10.0.0",
"tsconfig-paths": "4.1.0",
"typescript": "^4.7.4"
},
"jest": {
"moduleFileExtensions": [
"js",
"json",
"ts"
],
"rootDir": "src",
"testRegex": ".*\\.spec\\.ts$",
"transform": {
"^.+\\.(t|j)s$": "ts-jest"
},
"collectCoverageFrom": [
"**/*.(t|j)s"
],
"coverageDirectory": "../coverage",
"testEnvironment": "node"
}
}
The problem is there is an error while I'm trying to build my backend application with
docker-compose up
command.
The error is like this:
> [apps-shadowing-list-backend 5/8] RUN npm install:
#0 836.2 npm ERR! code FETCH_ERROR
#0 836.2 npm ERR! errno FETCH_ERROR
#0 836.2 npm ERR! invalid json response body at https://registry.npmjs.org/ts-jest reason: Invalid response body while trying to fetch https://registry.npmjs.org/ts-jest: Socket timeout
#0 836.2
#0 836.2 npm ERR! A complete log of this run can be found in:
#0 836.2 npm ERR! /root/.npm/_logs/2023-01-23T04_19_52_861Z-debug-0.log
------
failed to solve: executor failed running [/bin/sh -c npm install]: exit code: 1
And also there were some trouble in volumes of backend application. The mounting is not working properly.
I expected this backend application can communicate with prisma service by using graphql in nest js. And also changes have to be applied while it's running on docker container.