I got tired of copy-pasting Docker errors into Google. So I built a thin Python wrapper that sits transparently in front of the docker binary and translates failures into plain-English fixes in real time.
How it works:
bugtalk setup puts a wrapper script at /usr/local/lib/bugtalk/bin/docker and prepends it to PATH
The real docker binary path is stored as an absolute path, no recursion, no PATH games
On failure, stderr is matched against 25 regex patterns with OS-specific fix commands
Exit codes are always preserved, so CI/CD pipelines are completely unaffected
Interactive commands (docker exec -it, docker run -it) are detected by TTY flags and passed through with zero capture — so shell sessions work normally
errors.json updates weekly from GitHub in a background thread no reinstall ever needed
Install:
pip install bugtalk
bugtalk setup
That's it. Restart your shell. Docker just feels smarter.
Would love feedback on: edge cases I haven't handled, patterns worth adding to errors.json, and whether the PATH interception approach has failure modes I've missed on your setup.
mikael01ultra•45m ago
How it works: bugtalk setup puts a wrapper script at /usr/local/lib/bugtalk/bin/docker and prepends it to PATH The real docker binary path is stored as an absolute path, no recursion, no PATH games On failure, stderr is matched against 25 regex patterns with OS-specific fix commands Exit codes are always preserved, so CI/CD pipelines are completely unaffected Interactive commands (docker exec -it, docker run -it) are detected by TTY flags and passed through with zero capture — so shell sessions work normally errors.json updates weekly from GitHub in a background thread no reinstall ever needed
Install: pip install bugtalk bugtalk setup
That's it. Restart your shell. Docker just feels smarter.
Would love feedback on: edge cases I haven't handled, patterns worth adding to errors.json, and whether the PATH interception approach has failure modes I've missed on your setup.