Refactor docker download logic to use common_download_file_single with is_docker parameter #22
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.
This PR consolidates the docker blob download functionality into the existing
common_download_file_singlefunction, eliminating code duplication and simplifying the download architecture.Changes Made
1. Enhanced
common_download_file_singlefunctionbool is_dockerparameter (defaults tofalse)is_docker=true, the function uses simplified download logic suitable for Docker registry blobs:.jsonfiles, no ETag/Last-Modified checks).tmptemporary files with atomic rename2. Removed
common_docker_download_blobfunctioncommon_download_file_singlewhenis_docker=true3. Updated docker model resolution flow
common_docker_resolve_modelto usecommon_download_file_single(url, path, token, false, true)common_init_from_paramstocommon_params_handle_model4. Updated existing function calls
common_download_file_singlenow explicitly passis_docker=falseBenefits
Backward Compatibility
This change is fully backward compatible:
The refactoring successfully addresses the original issue by removing
common_docker_download_bloband usingcommon_download_file_singlewith anis_dockerparameter, while moving docker resolution to the appropriate location in the parameter handling flow.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
ggml.ai/home/REDACTED/work/llama.cpp/llama.cpp/build/bin/test-arg-parser(dns block)huggingface.co/usr/lib/git-core/git-remote-https origin REDACTED(dns block)/home/REDACTED/work/llama.cpp/llama.cpp/build/bin/test-thread-safety -hf ggml-org/models -hff tinyllamas/stories15M-q4_0.gguf -ngl 99 -p The meaning of life is -n 128 -c 256 -ub 32 -np 4 -t 2(dns block)/home/REDACTED/work/llama.cpp/llama.cpp/build/bin/llama-eval-callback --hf-repo ggml-org/models --hf-file tinyllamas/stories260K.gguf --model stories260K.gguf --prompt hello --seed 42 -ngl 0(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.