Fix silent wget failures in DownloadFile causing corrupted .bak file downloads #588
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When downloading .bak files from HTTP servers during container creation, users experienced mysterious "corrupted file" errors despite files appearing to download successfully. The issue was caused by silent wget failures that weren't being detected or reported.
Problem
Users running commands like:
Would see:
Root Cause
The
DownloadFile
function ininternal/container/controller.go
was:runCmdInContainer()
but ignored the returned stdout/stderrWhen containers tried to access
localhost
URLs (which fails due to container networking), wget would fail silently.Solution
1. Added Comprehensive Error Detection
2. Fixed BusyBox Compatibility
3. Added File Validation
User Impact
Before Fix
After Fix
Users now get clear, actionable error messages and can use proper solutions:
https://example.com/files/database.bak
http://host.docker.internal:3000/files/database.bak
Testing
Fixes #566.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.