#208·lore

Integration tests failed because minio/minio:latest is no longer available

Author: vys1nCreated Sep 15, 2026Updated Sep 15, 2026
Labelsbugneeds-triage

Lore version

lore 0.9.1-nightly+0

Installation method

Built from source

Operating system / architecture

Linux -- x86_64

Steps to reproduce

From the repository root:

sudo docker compose -f lore-integration-tests/compose.yaml up

Description

The integration test environment currently fails during Docker Compose startup because the minio/minio image reference in lore-integration-tests/compose.yaml can no longer be pulled.

The Compose file currently uses:

minio: image: minio/minio

Running the integration environment locally results in:

✘ Image minio/minio Error pull access denied for minio/minio Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login'

Expected vs actual behavior

Expected behavior

Docker Compose should pull the required images and start the MinIO, DynamoDB Local, and Consul services so that the integration tests can run.

Actual behavior

Compose fails while pulling MinIO:

failed to resolve reference "docker.io/minio/minio:latest" ... pull access denied for minio/minio

The other services are subsequently interrupted because Compose stops after the MinIO pull fails.

Additional information

I tested replacing the MinIO image with the Quay-hosted image:

minio: image: quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z

With this change, the Compose environment starts successfully. MinIO reports:

MinIO Object Storage Server Version: RELEASE.2025-09-07T16-13-09Z API: http://127.0.0.1:9000 WebUI: http://127.0.0.1:9001

DynamoDB Local and both Consul services also start successfully.

This suggests that the integration test Compose configuration needs to be updated to use a currently available MinIO image, preferably with a pinned release rather than an unpinned latest tag.

The issue appears to be independent of changes in the integration tests themselves, as the failure occurs during Docker image resolution before the tests are executed.

Component

None

Server context

No response

Regression?

No response

Relevant logs or output

bash
➜  lore git:(adr-numbering) sudo docker compose --file lore-integration-tests/compose.yaml up
[sudo] password for vysin:
[+] up 1/1
 ✘ Image minio/minio Error pull access denied for minio/minio, repository does not exist or may require 'docker login'                                  4.1s
Error response from daemon: pull access denied for minio/minio, repository does not exist or may require 'docker login'