Cannot Umount Directory From Host To Container
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
Start by reading the compose.yml shown in the issue, focusing on the dev-frontend-node volume, working_dir, and command, then inspect /home/app inside the running container. Reproduce the missing package.json error and verify that packages/frontend is mounted and yarn can start; the issue provides no repository file or test to update.
Written by the indexing model from the issue text.
Description
I build compose.yml for buil container with nodejs official from strach
but all file to packages/frontend cannot read from container.
With error logs like this :
024-06-24 14:17:20 yarn run v1.22.22
2024-06-24 14:17:20 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-24 14:17:20 error Couldn't find a package.json file in "/home/app"
the code :
name: dev-syncmed-klinik
services:
#
dev-frontend-node:
image: node:alpine
container_name: dev-frontend
working_dir: /home/app
volumes:
- ./packages/frontend:/home/app # Adjust path if needed
networks:
dev-syncmed-network:
ipv4_address: 101.113.0.2
ports:
- "80:80"
command: "yarn run start"
dev-backend-node:
image: node:alpine
container_name: dev-backend
working_dir: /home/app
volumes:
- ./packages/backend:/home/app # Adjust path if needed
- test-data:/home/app
links:
- dev-mongodb
networks:
dev-syncmed-network:
ipv4_address: 101.113.0.3
ports:
- "5000:5000"
command: "yarn run start"
depends_on:
- dev-mongodb
dev-mongodb:
image: mongo:latest
container_name: dev-mongodb
environment:
MONGO_INITDB_ROOT_USERNAME: -
MONGO_INITDB_ROOT_PASSWORD: -
ports:
- "27017:27017"
volumes:
- mongodb-data:/data/db
networks:
dev-syncmed-network:
ipv4_address: 101.113.0.4
volumes:
mongodb-data:
name: dev-mongodb
driver: local
test-data:
driver: local
networks:
dev-syncmed-network:
driver: bridge
ipam:
config:
- subnet: 101.113.0.0/24
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 6.4k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/getting-started
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docker/getting-started#481 · 2 comments · 5 reactions ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
docker/getting-started#394 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
docker/getting-started#494 ·
-
Chat Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
docker/getting-started#482 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
docker/getting-started#477 ·
All issues in docker/getting-started
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·