VisionSystemsInc / VisionSystemsInc/vsi_common
Detect ADD/COPY failures, and mention .dockerignore
Open
Nobody has claimed this yet.
enhancement
just
- Dominant language
- Shell
- Stars
- 8
- Forks
- 9
- Avg merge
- 36m
- Merged PRs (30d)
- 1
Description
When build fails:
Step 9/15 : ADD requirements.txt /
ERROR: Service 'learned' failed to build: ADD failed: stat /var/lib/docker/tmp/docker-builder152000285/requirements.txt: no such file or directory
Maybe stderr should be teed, and parsed to look for these errors. When a no such file is seen, mention .dockerignore as a suggests place to check.
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.
Research direction
Start by locating the build-error handling that receives Docker's stderr; no source file or test is identified in the issue. Reproduce the shown ADD failure and check how ADD/COPY and “no such file” errors are currently surfaced. Done means the relevant error is detected and the message suggests checking .dockerignore.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100