-
Notifications
You must be signed in to change notification settings - Fork 3k
Open
Labels
area/container-imageenv/armRelated to the aarch64 architectureRelated to the aarch64 architectureenv/m1Impacts Apple M1 machinesImpacts Apple M1 machinesenv/podmankind/bugSomething isn't workingSomething isn't working
Description
[ERROR] DOCKER> Error occurred during container startup, shutting down...
[ERROR] DOCKER> I/O Error [Unable to pull 'icr.io/db2_community/db2:12.1.0.0' from registry 'icr.io' : {"message":"no image found in manifest list for architecture \"arm64\", variant \"v8\", OS \"linux\""} (Internal Server Error: 500)]
I'm surprised we don't have an issue for this already, since I ran all our tests on Mac a few years ago, but I can't find one. It seems unlikely that DB2 used to pass on ARM and started failing, and I've confirmed we haven't removed a guard in the pom. It might be that M4 fails but earlier ARM processors pass. I don't know if it's an ARM+Podman issue, or it fails with Docker as well. The following integration tests fail on my Mac.
integration-tests/jpa-db2integration-tests/hibernate-reactive-db2integration-tests/reactive-db2-client
#33104 is tracking a different issue (not ARM), but the solution in #33104 (comment) might help.
To reproduce:
- Remove the guards which disable the tests (!)
- Run
mvn clean verify -Dtest-containers -Dstart-containers -f integration-tests/jpa-db2
Metadata
Metadata
Assignees
Labels
area/container-imageenv/armRelated to the aarch64 architectureRelated to the aarch64 architectureenv/m1Impacts Apple M1 machinesImpacts Apple M1 machinesenv/podmankind/bugSomething isn't workingSomething isn't working