New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure Cosmos DB Docker container stopping #15865
Comments
After discussion, it seems there's a problem with ubuntu-latest (ubuntu-20.04) vmImage. ubuntu-18.04 works. Anyway to understand what has changed from 18 to 20? |
Hi @soenneker @DOMZE for questions regarding changes on hosted images - I would suggest to open a ticket in https://github.com/actions/virtual-environments to get right eyes on it. |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Should this be closed as Azure/azure-cosmos-db-emulator-docker#45 is still not yet fixed? |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Bump. See my last comment |
I got the same behavior on github action (Ubuntu 22.04.2 LTS) with step:
with following output:
|
Also have this issue, currently blocking us from running CosmosDB on azure devops pipelines |
I am also seeing this issue, I have been fighting this for two days now. I have tried to use an older version of Ubuntu but 18.04 has been retired by Microsoft Azure DevOps. Anyone got any work around for this? |
Right now we're using the cosmos emulator script that's included on the windows host. Another workaround might be using a real cosmos instance and clearing out the data before running tests against it. |
This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days |
Bump. Any updates? |
I'm running into this issue on an Apple M1 chipset but my colleague seems to be able to run the image just fine from a Windows machine. Nothing spit out of the verbose logs, the image quietly exits with code 0 like it ain't no thang.
|
I've just hit this issue, any updates for 2024? |
Copying from: Azure/azure-cosmos-dotnet-v3#3010
Describe the bug
Using Azure DevOps and a ubuntu-latest hosted agent, when starting the container, the container returns right away the following:
To Reproduce
Create an Azure DevOps pipeline with the following:
Expected behavior
The container should create the partitions and return "Started" at some point
Actual behavior
The container exits and the logs shows
Additional context
Can't use older images (tags) to see if the code has changes since, as it fails the evaluation time check
Is there something I can add as environment variable to get more logs out to diagnose the problem?
The text was updated successfully, but these errors were encountered: