slimtoolkit / slimtoolkit/slim
new version 1.25.2 'using default probe' if --http-probe not set
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Previous Versions:
If you run docker-slim build without param --http-probe this meant --http-probe=false as default as described in the README.
Now:
If you run docker-slim build without param --http-probe
docker-slim[build]: info=http.probe message='using default probe'
a default-probe is used.
No real problem, but no backward compatibility. Everyone who wants no probe has now to add the param --http-probe=false
Contributor guide
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 the README's documentation for docker-slim build and the --http-probe option, then trace the build command's default handling for that flag. Reproduce the command without --http-probe and verify that its behavior matches the documented default; the issue is done when backward-compatible default behavior is restored and the documentation and relevant checks agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100