mcollina / mcollina/dockerode-build
dockerode-build tries to pull even if image is present
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/mcollina/dockerode-build/blob/master/build.js#L75: docker.pull(from, function (err, stream) {
causes problems if you are trying to write new images on a box that does not have pull permission. I build a bunch of images (that descend from each other) on a dumb server then later push them up, but having dockerode-build messes up this flow.
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 with build.js at line 75 and trace how the image source is handled before docker.pull is called. Confirm the behavior when the image is already present locally, then test that building such an image no longer requires pull permission while dependent image builds still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100