mimirtool remote-read export fails

[pio-kol]

Describe the bug

mimirtool remote-read export fails

To Reproduce

Steps to reproduce the behavior:

1. Clone Mimir repo git clone https://github.com/grafana/mimir.git
2. Go to tutorial directory mimir/docs/sources/mimir/get-started/play-with-grafana-mimir
3. Run project docker compose up -d
4. Try to export data docker run grafana/mimirtool remote-read export --address=https://host.docker.internal:9009/ --id="anonymous"
5. Error is reported

docker run grafana/mimirtool remote-read export --address=https://host.docker.internal:9009/ --id="anonymous"
time="2024-10-18T10:05:13Z" level=info msg="Created remote read client using endpoint 'https://host.docker.internal:9009/prometheus/api/v1/read'"
time="2024-10-18T10:05:13Z" level=info msg="Created TSDB in path '/tmp/mimirtool-tsdb1342615180'"
time="2024-10-18T10:05:13Z" level=info msg="Querying time from=2024-10-18T09:05:13Z to=2024-10-18T10:05:13Z with selector=up"
time="2024-10-18T10:05:13Z" level=info msg="Store TSDB blocks in '/tmp/mimirtool-tsdb1342615180'"
mimirtool: error: process blocks: input: chunkedReader: message size exceeded the limit 0 bytes; got: 1763 bytes, try --help

Expected behavior

Export works correctly

Environment

• Infrastructure: laptop
• Deployment tool: docker compose (also reproduced with K8s cluster)

Additional Context

[pio-kol]

Most likely the issue was introduced by that commit / PR

This is the first version I've reproduced the problem with: Docker

This is a backport of the PR above: commit

[armandgrillet]

@krajorama Could you check if the PR mentioned by @pio-kol could have introduced this bug?

[pio-kol]

Do we have any update on the issue? Did you had a chance to reproduce it?