# devopsgym / testgen__containerd__containerd-10177

- taskset: [devopsgym](https://harnessreport.com/tasks/devopsgym.md)
- difficulty: hard
- category: test-generation
- language: 
- runnable from the site: no
- agent timeout: 3000s

## Results by harness

_none yet_

## Instruction

```
The following text contains a user issue (in <issue/> brackets) posted at a repository. Further, you are provided with file contents of several files in the repository that contain relevant code (in <code> brackets). It may be necessary to use code from third party dependencies or files not contained in the attached documents however. Your task is to identify the issue and implement a test case that verifies a proposed solution to this issue. More details at the end of this text.
<issue>
      ### What is the problem you're trying to solve

If I'm being correct, currently, each layer is downloaded in one goroutine within [`newHTTPReadSeeker`](https://github.com/azr/containerd/blob/7b76b4467f1e986c838b5001673425d0a2c55524/core/remotes/docker/fetcher.go#L57).
I work with quite big AI related images (drivers, models and deps are big), and sometimes, a layer can be really big, it is not rare at all to see ~10 GB layers.

I think it could benefit this use case to allow to parallelise the download of a single layer.

### Describe the solution you'd like

A way to configure the parallelisation of a layer would be nice to have.

I know that the `amazon-ecr-containerd-resolver` uses parallelisation with htcat: https://github.com/awslabs/amazon-ecr-containerd-resolver/blob/dc8a230a63b583bda4e0601a8945b4fdf9166084/ecr/fetcher.go#L125

If that setting is set, htcat tries to do range requests on big enough files and if that works, downloads things in parallel.

### Additional context

happy to work on this.

Related: https://github.com/containerd/containerd/pull/9138

</issue>
Please generate test cases that check whether an implemented solution resolves the issue of the user (at the top, within <issue/> brackets).
You may apply changes to several files.
Apply as much reasoning as you please and see necessary.
Make sure to implement only test cases and don't try to fix the issue itself.
You are not allowed to read git history.
```
---
Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp