You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running cosmosdb_test, it fails for timeout when waiting for the Docker image (https://mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest) to start (see logs section below).
This happens to users with Mac with an Apple chip (and runs OK on the CI).
Expected behavior
The test passes.
lakeFS version
v1.43.0 (and above)
How lakeFS is installed
No response
Affected clients
No response
Relevant log output
2025/01/06 10:34:43 Waiting up to 5m0s for emulator to start
2025/01/06 10:39:41 Could not connect to Docker: could not connect to cosmosdb emulator at https://localhost:55035: reached retry deadline: Get "https://localhost:55035/_explorer/emulator.pem": dial tcp [::1]:55035: connect: connection refused
FAIL github.com/treeverse/lakefs/pkg/kv/cosmosdb 299.548s
Contact details
No response
The text was updated successfully, but these errors were encountered:
This test is trying to run this docker image: mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest
When running docker ps -a I noticed this image ran and exited with status code 139 which probably indicates it tried to access a memory location to which it does not have access.
From the docs it seems like this emulator is not supported for mac.
What happened?
When running
cosmosdb_test
, it fails for timeout when waiting for the Docker image (https://mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator:latest
) to start (seelogs
section below).This happens to users with Mac with an Apple chip (and runs OK on the CI).
Expected behavior
The test passes.
lakeFS version
v1.43.0 (and above)
How lakeFS is installed
No response
Affected clients
No response
Relevant log output
Contact details
No response
The text was updated successfully, but these errors were encountered: